Volumes cannot be referred to using shorter IDs
When referring to volumes on the CLI, they cannot be addressed using short IDs, like containers and images, only by the full ID:
$ hyper volume create
dc1ec072da927a2b138702a99a26f22557b53941eae78632aeae9260a0c8d25
$ hyper volume inspect dc1ec
[]
Error: No such volume: dc1ec
$ hyper volume rm dc1ec
Error response from daemon: No such volume: dc1ec
$ hyper volume rm dc1ec072da927a2b138702a99a26f22557b53941eae78632aeae9260a0c8d25
dc1ec072da927a2b138702a99a26f22557b53941eae78632aeae9260a0c8d25
Hello @paetling
Current, you can not operate the volume with short ID, but you may try --name to specify a volume name to operate, what do you think?
Thanks,
--name can be useful as a workaround for the moment, but short IDs would really be more consistent with every other command.
On Tue, 8 Nov 2016, 20:16 Lei Xue [email protected] wrote:
Hello @paetling https://github.com/paetling
Current, you can not operate the volume with short ID, but you may try --name to specify a volume name to operate, what do you think?
Thanks,
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hyperhq/hypercli/issues/177#issuecomment-259063525, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJgi5XQkr1HM5xYz1FnbW5tn1oSEtGGks5q8CG3gaJpZM4KsBYA .