Skip to content
This repository has been archived by the owner on Feb 8, 2021. It is now read-only.

Volumes cannot be referred to using shorter IDs #177

Open
passcod opened this issue Nov 8, 2016 · 2 comments
Open

Volumes cannot be referred to using shorter IDs #177

passcod opened this issue Nov 8, 2016 · 2 comments

Comments

@passcod
Copy link

passcod commented Nov 8, 2016

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
@carmark
Copy link
Contributor

carmark commented Nov 8, 2016

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,

@passcod
Copy link
Author

passcod commented Nov 8, 2016

--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 notifications@github.com 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
#177 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJgi5XQkr1HM5xYz1FnbW5tn1oSEtGGks5q8CG3gaJpZM4KsBYA
.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants