magicmopper

Results 12 comments of magicmopper
trafficstars

i had the same problem kfctl version: kfctl_v1.0.1-0-gf3edb9b_linux.tar.gz kubernetes version: 1.18.0 linux :centos7.7 (vm)

same problem version: 2.5.0

@imeoer It looks like the configuration file cannot be found. ``` root@nydus:/var/log# /usr/local/bin/containerd-nydus-grpc --config /etc/nydus/config.toml INFO[2023-11-13T11:03:06.544513712+08:00] Start nydus-snapshotter. Version: v0.13.3, PID: 104187, FsDriver: fusedev, DaemonMode: dedicated INFO[2023-11-13T11:03:06.545149122+08:00] parsed cgroup config:...

> @jokerwenxiao Have you completed step 5? If completed, try restarting the containerd and dockerd services. > > ``` > sudo systemctl restart containerd > sudo systemctl restart docker >...

change step 2 command `wget -O /etc/nydus/nydusd-config.json https://raw.githubusercontent.com/containerd/nydus-snapshotter/"$TAG"/misc/snapshotter/nydusd-config.fusedev.json` to `wget -O /etc/nydus/nydusd-config.fusedev.json https://raw.githubusercontent.com/containerd/nydus-snapshotter/"$TAG"/misc/snapshotter/nydusd-config.fusedev.json` can solve it. but there is a new problem: ``` root@nydus:/var/log# docker run -d --restart=always -p 5000:5000...

> change step 2 command `wget -O /etc/nydus/nydusd-config.json https://raw.githubusercontent.com/containerd/nydus-snapshotter/"$TAG"/misc/snapshotter/nydusd-config.fusedev.json` to `wget -O /etc/nydus/nydusd-config.fusedev.json https://raw.githubusercontent.com/containerd/nydus-snapshotter/"$TAG"/misc/snapshotter/nydusd-config.fusedev.json` can solve it. > > but there is a new problem: > > ``` > root@nydus:/var/log#...

> 1. Make sure all nydus image and the containers using nydus image has been removed, and no nydusd processes: `ps aux | grep nydusd`; > 2. If the nydus...

> It seems that some snapshots have not been reclaimed, maybe containerd hasn't started GC? Can you find any files in these snapshot directories? just like this: ``` root@node1:/var/lib/containerd-nydus/snapshots# tree...

> If no nydusd processes are alive and the snapshot directories can be accessed, these snapshots should belong to the OCI v1 images, maybe try to remove the OCI v1...

I found that when I execute `docker rmi`, the layers of image in directory `/var/lib/containerd/io.containerd.content.v1.content/blobs/sha256` are not deleted.