dangling images do not go away with 'podman image prune'
Hello, I see a lot of so called dangling images with $ podman images | more REPOSITORY TAG IMAGE ID CREATED SIZE localhost/sles15-sp6-v73 latest fcdbe8e4e245 21 hours ago 15.3 GB <none> <none> e84f83f1637c 4 days ago 20.2 GB <none> <none> d3921b019185 4 days ago 18.3 GB ... $ podman images | grep '<none>' | wc -l 34 Yesterday, the number was even 57, then I did 'podman image prune' and even 'podman image prune -a', the latter with the effect that I have had to re-build my container 'localhost/sles15-sp6-v73'. But even after the '-a' the dangling ones did not went away completely. This causes a serious disk space problem. I run the 'podman images' into a file, edited it a bit to sum up the used space with bc(1): $ cat sum-space-with-bc.sh echo '15300+ 20200+ 18300+ 13700+ 13600+ 13600+ 13300+ 13300+ 7670+ 7650+ 7630+ 7130+ 4330+ 4240+ 4240+ 4240+ 1530+ 568+ 568+ 568+ 568+ 568+ 568+ 568+ 7150+ 7600+ 7510+ 7200+ 6230+ 8840+ 5850+ 5520+ 5520+ 5520+ 5520+ 5520+ 8360+ 130' | bc $ sh sum-space-with-bc.sh 260406 This number 260 GB matches nearly what I do see in the file system: # du -sh storage/* 1.0K storage/defaultNetworkBackend 1.3M storage/libpod 266G storage/overlay ^^^^ 2.1M storage/overlay-containers 8.3M storage/overlay-images 71M storage/overlay-layers 1.0K storage/storage.lock 0 storage/userns.lock The podman version is 4.7.2 and the OS is SuSE SLES 15 SP6. Should I file an issue in https://github.com/containers/podman/issues ? Thanks matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub Annalena Baerbock: "We are fighting a war against Russia ..." (25.1.2023) I, Matthias, I am not at war with Russia. Я не воюю с Россией. Ich bin nicht im Krieg mit Russland.
participants (1)
-
Matthias Apitz