-
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' requires complete volume name instead of unambiguous volume name #3891
Comments
I think we went a bit too far when fixing #3635 then. I'll take this one. |
Hm. I'm actually not sure this is intended to work. Docker requires a full volume name to remove a volume; We could consider adding this, but I'm retagging as a feature request, not a bug, given this doesn't appear to be Docker behavior. |
I think we want to allow these lookup operations only for volume commands - Adding volumes to containers with |
@mheon I am sorry that I did not take a look at Docker first. |
This isn't included in Docker, but seems handy enough. Use the new API for 'volume rm' and 'volume inspect'. Fixes containers#3891 Signed-off-by: Matthew Heon <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman volume rm
requires the complete volume name whereas containers can be identified by an unambiguous abbreviation of their name.Steps to reproduce the issue:
podman volume create a
podman volume create insanelylonghashstring
# i unambiguously identifies insanelylonghashstring
podman volume rm i
Describe the results you received:
Error: volume with name i not found: no such volume
, volume still existingDescribe the results you expected:
insanelylonghashstring
, volume removedAdditional information you deem important (e.g. issue happens only occasionally):
May be related to #3635.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: