-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
'volume rm' removes an arbitrary volume if the volume name is ambiguous #3635
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.
Comments
openshift-ci-robot
added
the
kind/bug
Categorizes issue or PR as related to a bug.
label
Jul 23, 2019
I'll take this one - pretty sure I know where the problem is. |
mheon
added a commit
to mheon/libpod
that referenced
this issue
Jul 24, 2019
We should not be fuzzy matching on image names. Docker doesn't do it, and it doesn't make much sense. Fixes containers#3635 Signed-off-by: Matthew Heon <matthew.heon@pm.me>
#3641 to fix |
mheon
added a commit
to mheon/libpod
that referenced
this issue
Jul 24, 2019
We should not be fuzzy matching on image names. Docker doesn't do it, and it doesn't make much sense. Fixes containers#3635 Signed-off-by: Matthew Heon <matthew.heon@pm.me>
Thank you! |
mheon
added a commit
to mheon/libpod
that referenced
this issue
Jul 25, 2019
We should not be fuzzy matching on volume names. Docker doesn't do it, and it doesn't make much sense. Everything requires exact matches for names - only IDs allow partial matches. Fixes containers#3635 Signed-off-by: Matthew Heon <matthew.heon@pm.me>
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 24, 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.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
If there are multiple volumes whose names start with the same character(s) (such as
a1
,a2
) thenpodman volume rm a
removes one of these volumes althougha
is ambiguous. This concerns named volumes as well as volumes identified by their hashes.Steps to reproduce the issue:
podman volume create a1
podman volume create a2
podman volume rm a
Describe the results you received:
Either volume
a1
ora2
is removed.Describe the results you expected:
Podman should not remove any volume. Instead it should complain about the ambiguous volume name.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: