fahed dorgaa

> I still prefer shelling out buildctl. Could you please elaborate on why you prefer shelling instead of using the SDK? In [DIB](https://github.com/radiofrance/dib), we currently [shell](https://github.com/radiofrance/dib/blob/f47eede11e3e09702883abc85ca98b6dc1d06f69/cmd/build.go#L185) out to the `buildctl`...

thank you @abitrolly , `shellcheck` CI is failing

The logic for IO persistence [has been moved](https://github.com/containerd/nerdctl/blob/main/pkg/taskutil/taskutil.go#L132) to the nerdctl side; when nerdctl exits, things stop. In an ideal world, this logic should be handled by the shim. I...

> Are we even responsible for writing logs at any point? Or is it containerd only? Three main components in log management: - `containerd-shim` redirects logs from `runc` to the...

> Well, am I not a user? 😁 (a high maintenance one, for sure...) I was pointing to the CI, the error was detected after multiple CI retries ^^

Hi @Shubhranshu153, I think no need to access the `userns` of pause container you can just copy these files from host /proc rootfs of pause container to the attachable container

@fuweid I think that should be closed :)

@fuweid as you told me after lower the dirty page ratio, the issue is gone! Also I think if we cannot guarantee the system can be shutdown gracefully it is...

Good point but as open source product our first target is to fill the oci distribution requirement. Hard to satisfy all oci distribution implemention (Hub, harbor..). Otherwise fork nerdctl and...

why doing this ? almost of drivers are called from binaries. IMO, not installing the driver binary should be is enough.