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

volume created via WebUI not usable directly #12

Closed
xinity opened this issue May 9, 2017 · 2 comments
Closed

volume created via WebUI not usable directly #12

xinity opened this issue May 9, 2017 · 2 comments

Comments

@xinity
Copy link

xinity commented May 9, 2017

Hi,

going further on test LongHorn, i've found something strange,
i've created 3 volumes via the WebUI .
on a node, here's what i have:

docker volume ls
DRIVER              VOLUME NAME
local               033816fae07fd2075579606ef1e89647198fdba359c17f26a99ddde6b6b83905
local               19c66b299999da7281a2b3790d7c8c35cdb80f9dbe6c6b09a00f5b429c6d9133
local               4491e34682b18821a9f15b135524db252e2b00d29bb3c7571c0668ae45b42e3e
local               7a4a251058bde34b71689bbcaeea2a6c306fa28160d2755f2cf7c469088a937a
local               96e1437ddba02155fc21eac5e7241d43ef6145dc0a539a66335c2efdba154713
local               bc93ca1ba1449d6759ce50bb3364ec5a85f4cb4b1739983f3c9aceb927201101
local               c0b3f21dec349e0319c92c9ceda97b730328255333aef17a4fc803cc4fa4af51
local               de645596f80be62b0f29d8f4503f011977abfbbe1f3619573e31d78d33f85f08
local               eb8245263edea416da72985e895d6c75f78094f526d008104eb0626ca3da5f02

if i do : docker volume create -d longhorn vol2XinityTest

if have suddenly these volumes available:

docker volume ls
DRIVER              VOLUME NAME
local               033816fae07fd2075579606ef1e89647198fdba359c17f26a99ddde6b6b83905
local               19c66b299999da7281a2b3790d7c8c35cdb80f9dbe6c6b09a00f5b429c6d9133
local               4491e34682b18821a9f15b135524db252e2b00d29bb3c7571c0668ae45b42e3e
local               6e9a04b525cbae78023af6c82282b76ea7cd029a6ab41a67a8c4e73b47d0eb45
local               7a4a251058bde34b71689bbcaeea2a6c306fa28160d2755f2cf7c469088a937a
local               8e1c21a1b1c9245ca160faa0390230181030ebf72ba9d6915c2f236183116fde
local               96e1437ddba02155fc21eac5e7241d43ef6145dc0a539a66335c2efdba154713
longhorn            Xinity_Vol1
longhorn            Xinity_Vol2
longhorn            Xinity_Vol3
local               bc93ca1ba1449d6759ce50bb3364ec5a85f4cb4b1739983f3c9aceb927201101
local               c0b3f21dec349e0319c92c9ceda97b730328255333aef17a4fc803cc4fa4af51
local               de645596f80be62b0f29d8f4503f011977abfbbe1f3619573e31d78d33f85f08
local               eb8245263edea416da72985e895d6c75f78094f526d008104eb0626ca3da5f02
longhorn            vol1XinityTest
longhorn            vol2XinityTest

Have i did something wrong ?
How can i have the volumes created via the WebUI directly available ?

Thanks a lot !

@yasker
Copy link
Member

yasker commented May 9, 2017

@xinity

Even you don't see it in the docker volume ls, it's still available to use with your container.

Just try docker run -it --volume-driver longhorn -v Xinity_Vol1:/vol1 ubuntu before you use docker command to create another volume, you should see the volume in your container.

I think Docker doesn't show it because you haven't used longhorn driver before so Docker doesn't ask longhorn for a list of volume. These will be automatically done when first time you use the driver.

@yasker yasker closed this as completed May 9, 2017
@xinity
Copy link
Author

xinity commented May 9, 2017 via email

mantissahz pushed a commit to mantissahz/longhorn that referenced this issue Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants