imeoer

@alexellis Thanks, will continue to follow the issue later.

Any error logs are output from nydus-snapshotter for the ubuntu:20.04 image? The problem doesn't seem to be nydus related (ubuntu:20.04 is not a nydus image), have you tried removing `--snapshotter...

There are no exceptions in the nydus snapshotter logs, please check if it is related to the access permissions of the directory where `/home/inklesspen/.local/share/containerd-nydus/snapshots/1/fs/var/cache/apt/archives/partial` is located, e.g., the access perm...

Does it mean we must use `$containerd_root_dir/io.containerd.snapshotter.v1.nydus` as the root dir of nydus snapshotter?

We still need to ensure no error messages are thrown, right? Although maybe it doesn't have any effect.

Hi @Riverdd, is it convenient for you to join DingTalk group `34971767` ?

Related fixup on containerd: https://github.com/containerd/containerd/pull/10127

> Related fixup on containerd: [containerd/containerd#10127](https://github.com/containerd/containerd/pull/10127) But we'd better still set snapshotter's default root path to `/var/lib/containerd/io.containerd.snapshotter.v1.nydus` for the better compatibility.

It seems this error happened earlier: ``` time="2023-11-03T00:41:42.464732357Z" level=warning msg="snapshot garbage collection failed" error="error reading from server: EOF: unavailable" snapshotter=nydus ``` It looks like the nydusd HTTP API server is...

> The already running nydusd should not change its configuration I suppose. The newly created nydusd can use the new nydusd configuration. Otherwise, it's not easy to handle the consistency...