jmaitrehenry / docker-azurefile-plugin Goto Github PK

I'm wondering if it's possibile to customize not only AZURE_STORAGE_ACCOUNT and AZURE_STORAGE_ACCOUNT_KEY, as stated in the main doc page, but the full Azure connection string, too.

My use case is to try the plugin using a local-running azurite installation, so providing my own storage account and storage account key is not enough form me - I should provide something like AZURE_CONNECTION_STRING=DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://containerRunningAzurite:10000/devstoreaccount1;QueueEndpoint=http://containerRunningAzurite:10001/devstoreaccount1;

Is there already a way to do something like this?
Thank you in advance!

Add the mfsymlinks option when mounting the volume to support symbolic links.

Hi Julien,

do you plan on supporting azure blob storage as well? I'm pretty new to the docker world and am looking for an easy way to mount blob containers without modifying the docker container and am overwhelmed by this. There seems to be support for s3 but none (afaik) for azure without fiddling around with minio :(

Any help would be appreciated

When I run
$ docker volume create --name my_volume -d jmaitrehenry/azurefile
It shows this error msg.
Error response from daemon: create az_volume: VolumeDriver.Create: error creating azure file share: storage: service returned error: StatusCode=400, ErrorCode=InvalidResourceName, ErrorMessage=The specifed resource name contains invalid characters.

I think volume name can't contain underscore.

Julien, thanks for updating this storage driver. Can you offer any syntax guidance on using this storage driver from a compose fileb(stack deploy in Swarm mode)? It worked great from simple docker run commands, but have been unable to get a deployment to a host with the plug-in installed to work from a compose file. Any guidance your can offer is appreciated.

UPDATE: Julien, but enabling debug in Docker daemon, I was able to find the solution through considerable trial and error.

Need some documentation. When you got to Azure, and setup a file share, for example, it provides some data. How does that translate to the parameters here?

For example,
mount -v -t cifs //ABC.file.core.windows.net/XYZ /mnt/mymount -o nofail,vers=3.0,credentials=/etc/smbcredentials/ABC.cred,dir_mode=0777,file_mode=0777,serverino

I've taken the smbcredentials for the initial plugin install, but beyond that it is not clear how the volume creation should take what the CNAME should be (like ABC above), and what the subdirectory /path should be like (like XYZ above).

Also, there is no way to pass serverino, or nofail...

What -o options should I pass so the URL and path are correct, StorageBase, Share, Remotepath? How do I pass the additional options which are rejected?