New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User can delete images, even when used by root containers (with additionalimagestores) #13003
Comments
The issue is that the "additionalStore" knows nothing about its images being used in other stores, and there is no way to know. So I think this should just be documented in troubleshooting. |
Thanks for the feedback. |
I am also facing the same issue but in the case of pod creation. |
A friendly reminder that this issue had no activity for 30 days. |
Closes: containers#13003 [NO NEW TESTS NEEDED] Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
PR here: #13590 |
Closes: containers#13003 [NO NEW TESTS NEEDED] Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Closes: containers#13003 [NO NEW TESTS NEEDED] Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Closes: containers#13003 [NO NEW TESTS NEEDED] Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When adding the graphRoot of a user podman to the additionalimagestores of root podman images from user podman are deleted even if there are existing containers in root podman.
Maybe a known issue, but the shortcomings are not very specific in this regard.
Steps to reproduce the issue:
add graphRoot of user podman (e.g.
/home/vagrant/.local/share/containers/storage
) toadditionalimagestores
in/etc/containers/storage.conf
pull image in user podman:
podman pull hello-world
create container as root with image pulled by rootless podman:
sudo podman create --name test hello-world
delete image as user:
podman rmi hello-world
Describe the results you received:
image is deleted:
root container is still present but (understandably) unable to start:
Describe the results you expected:
Image deletion should fail, as it would if the user podman had containers created with that image, e.g.
Output of
podman version
:Output of
podman info --debug
:Output of
sudo podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
No
Additional environment details (AWS, VirtualBox, physical, etc.):
Tested in Vagrant box:
The text was updated successfully, but these errors were encountered: