Skip to content
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

podman-remote: rm -a --volumes: does not remove volumes #7128

Closed
edsantiago opened this issue Jul 28, 2020 · 0 comments · Fixed by #7222
Closed

podman-remote: rm -a --volumes: does not remove volumes #7128

edsantiago opened this issue Jul 28, 2020 · 0 comments · Fixed by #7222
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote

Comments

@edsantiago
Copy link
Member

In window 1:

$ ./bin/podman system service --timeout=0

In window 2:

$  ./bin/podman-remote run -v /myvol alpine date
Tue Jul 28 21:22:16 UTC 2020

$ ./bin/podman-remote rm -a --volumes
9f3ca8048c2c627be3d828071b543b6557613715ded72be65a4dc480983b3c85

$ ./bin/podman-remote volume ls
DRIVER      VOLUME NAME
local       f652d1def911a5580319f9ced3c77eef98a0f659eefb755acd9ece2ef7a3d887

With non-remote podman, the final volume ls produces empty results. It is not a race condition, the volume persists until manually removed with podman volume rm -a.

@edsantiago edsantiago added kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote labels Jul 28, 2020
baude added a commit to baude/podman that referenced this issue Aug 4, 2020
the go binding for remove container was using 'vols' for a key to remove volumes associated to the container.  the correct key should be "v" and is documented as such.

Fixes: containers#7128

Signed-off-by: Brent Baude <bbaude@redhat.com>
vrothberg pushed a commit to vrothberg/libpod that referenced this issue Aug 11, 2020
the go binding for remove container was using 'vols' for a key to remove volumes associated to the container.  the correct key should be "v" and is documented as such.

Fixes: containers#7128

Signed-off-by: Brent Baude <bbaude@redhat.com>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant