I have rmi the image, but when I pull it again, it shows "already exists".
I have rmi the image, but when I pull it again, it shows "already exists". $ podman images REPOSITORY TAG IMAGE ID CREATED SIZE myregistry.com/centos 7.9.2009 eeb6ee3f44bd 10 months ago 212 MB $ podman rmi eeb6ee3f44bd Untagged: myregistry.com/centos:7.9.2009 Deleted: eeb6ee3f44bd0b5103bb561b4c16bcb82328cfe5809ab675bb17ab3a16c517c9 $ podman pull myregistry.com/centos:7.9.2009 Trying to pull myregistry.com/centos:7.9.2009... Getting image source signatures Copying blob 0b2dc63a68b9 skipped: already exists Copying config eeb6ee3f44 done Writing manifest to image destination Storing signatures eeb6ee3f44bd0b5103bb561b4c16bcb82328cfe5809ab675bb17ab3a16c517c9
Thanks for reaching out. On Mon, Aug 8, 2022 at 10:49 AM None via Podman <podman@lists.podman.io> wrote:
I have rmi the image, but when I pull it again, it shows "already exists".
$ podman images REPOSITORY TAG IMAGE ID CREATED SIZE myregistry.com/centos 7.9.2009 eeb6ee3f44bd 10 months ago 212 MB
$ podman rmi eeb6ee3f44bd Untagged: myregistry.com/centos:7.9.2009 Deleted: eeb6ee3f44bd0b5103bb561b4c16bcb82328cfe5809ab675bb17ab3a16c517c9
$ podman pull myregistry.com/centos:7.9.2009 Trying to pull myregistry.com/centos:7.9.2009... Getting image source signatures Copying blob 0b2dc63a68b9 skipped: already exists
That indicates the specific "blob" (i.e., the layer) is already present in the local storage. `rmi` may remove the entire image but it will not remove a layer that is used by another image. You can run `$ podman image tree --whatrequires centos:7.9.2009` to figure out which image is using this layer.
Copying config eeb6ee3f44 done Writing manifest to image destination Storing signatures eeb6ee3f44bd0b5103bb561b4c16bcb82328cfe5809ab675bb17ab3a16c517c9 _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
participants (2)
-
ugiwgh@qq.com -
Valentin Rothberg