-
Notifications
You must be signed in to change notification settings - Fork 55
remotepath throws error #63
Comments
This looks interesting. I am not familiar with SMB and UNC paths myself. Does it work fine without the @zlatan any ideas if you see any issues with the UNC syntax, or how did it work for you? |
Yes, as I wrote in the first command, it works when I don't use |
@ahmetalpbalkan I reproduced the problem. In current implementation 'remotepath' work with only one level of depth, @mrmunch have two. |
@zlatan So the |
Hmm is this like we're constructing a bad UNC or is this an unsupported feature? |
I have done some more testing, and if 'remotepath' is used, on the first time the volume is created it errors. I appears the UNC path is missing a prepending '/'
Subsequently the volume object exists and so doesn't present any errors, it just doesn't work. |
@zlatan I think I found a bug. This piece of code azurefile-dockervolumedriver/driver.go Lines 306 to 309 in 81e6f45
remotepath into a string like //host/share .
However path.Join assumes I will submit a fix. |
@williamayerst @mrmunch can you please try If it works for you I will tag and release it as |
Hurrah, I will check and let you know on Monday, thanks! |
@ahmetalpbalkan Yes, it's a bug. |
@ahmetalpbalkan I can confirm it works now! I also tested it with |
Thanks. |
I have an Azure Storage account called
mystorageaccount
with a file share calledmyshare
and a directory inside this share calledmydir
.works:
docker run -it -v $(docker volume create -d azurefile -o share=myshare):/data ubuntu
doesn't work:
docker run -it -v $(docker volume create -d azurefile -o share=myshare -o remotepath=mydir):/data ubuntu
I get:
The text was updated successfully, but these errors were encountered: