-
|
Hi, I compared disk space usage between CRI-O and Containerd and found multiple difference in consumption. For example, the same image root@crio:~# crictl images -f reference=nginx
IMAGE TAG IMAGE ID SIZE
docker.io/library/nginx 1.25.5 e784f4560448b 192MB
root@containerd:~# crictl images -f reference=nginx
IMAGE TAG IMAGE ID SIZE
docker.io/library/nginx 1.25.5 e784f4560448b 71MBThus, using the same set of images on the nodes, there is a large difference in the amount of disk space used: root@crio:~# du -sh /var/lib/containers
2.4G /var/lib/containers
2.4G total
root@containerd:~# du -sh /var/lib/containerd
939M /var/lib/containerdContainerd has the option |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
@mtrmac @giuseppe I don't know the background--what was the motivation of storing images untarred on disk? could this have something to do with it? |
Beta Was this translation helpful? Give feedback.
-
|
storing them tarred is not really useful as you can't use them, you need to extract them first. I expect containerd to do the same if you are using overlay. Can you check the difference before and after pulling the same image? |
Beta Was this translation helpful? Give feedback.
-
|
something strange) after pulling image size of containerd dir also increased on ~ 192M: root@containerd:~# du -sch /var/lib/containerd/
740M /var/lib/containerd/
740M total
root@containerd:~# crictl pull nginx:1.25.5
Image is up to date for sha256:e784f4560448b14a66f55c26e1b4dad2c2877cc73d001b7cd0b18e24a700a070
root@containerd:~# du -sch /var/lib/containerd/
933M /var/lib/containerd/
933M total
root@containerd:~# crictl images -f reference=nginx
IMAGE TAG IMAGE ID SIZE
docker.io/library/nginx 1.25.5 e784f4560448b 71MB
root@containerd:~# du -sch /var/lib/containerd/
933M /var/lib/containerd/
933M totalIt looks like At the same time, checking via ncdu shows that there is no difference with containerd: ncduThe total size of the disk used also confirms this: df -h |
Beta Was this translation helpful? Give feedback.
-
|
The problem is related to the overlay mount points. By default cri-o stores them in This is the reason why
Then the results become similar: thanks for help! |
Beta Was this translation helpful? Give feedback.
-
|
great I'm glad you figured it out. Thanks for opening! I'm gonna close this |
Beta Was this translation helpful? Give feedback.
The problem is related to the overlay mount points. By default cri-o stores them in
/var/lib/containers/storage/overlaywhile containerd does it in/run/containerd/io.containerd.runtime.v2.taskThis is the reason why
du -schshows different results. For correct check withduwe can use arg-x:-x, --one-file-system skip directories on different file systemsThen the results become similar:
thanks for help!