Azure / azurefile-dockervolumedriver

Docker Volume Driver for Azure File Service over SMB/CIFS :whale:
Apache License 2.0
169 stars 57 forks source link

Mount error while using volume driver in Ubuntu 16.10 #88

Closed sreejith-mq closed 6 years ago

sreejith-mq commented 7 years ago

I am getting a mount error while using azurefile volume driver. The system details are as follows OS: Ubuntu 16.10 Docker version: 1.12.6 Azurefile version: 0.5.1

I installed the plugin as per instructions. cifs-utils was installed as well.
The azurefile service as well as docker service is running. I created a volume using docker volume create -d azurefile --name test -o share=test At this point I got the following error in the log for azurefile service

Apr 21 17:49:14 ubuntu azfile[28162]: time="2017-04-21T17:49:14+05:30" level=error msg="could not fetch metadata: cannot read metadata: open /etc/docker/plugins/azurefile/volumes/test1: no such file or director
y" name=test1 operation=get
Apr 21 17:49:14 ubuntu azfile[28162]: time="2017-04-21T17:49:14+05:30" level=debug msg="request accepted" name=test1 operation=create options=map[share:test1b]
Apr 21 17:49:14 ubuntu azfile[28162]: time="2017-04-21T17:49:14+05:30" level=info msg="created azure file share \"test1b\"" name=test1 operation=create options=map[share:test1b]
Apr 21 17:49:14 ubuntu azfile[28162]: time="2017-04-21T17:49:14+05:30" level=debug msg="request accepted" name=test1 operation=path

However the file share was created successfully in azure Then I tried using the volume with docker volume run -it --rm -v test:/data busybox This resulted in a long hang by docker. Meanwhile the following logs were generated

Apr 21 17:50:43 ubuntu azfile[28162]: time="2017-04-21T17:50:43+05:30" level=debug msg="request accepted" name=test1 operation=mount
Apr 21 17:52:45 ubuntu azfile[28162]: time="2017-04-21T17:52:45+05:30" level=error msg="mount failed: exit status 32\noutput=\"mount.cifs kernel mount options: ip=168.63.161.178,unc=\\\\\\\\glydata.file.core.wi
ndows.net\\\\test1b,vers=3.0,file_mode=0777,dir_mode=0777,uid=0,gid=0,user=glydata,pass=********\\nmount error(11): Resource temporarily unavailable\\nRefer to the mount.cifs(8) manual page (e.g. man mount.cifs
)\\n\"" name=test1 operation=mount
Apr 21 17:52:45 ubuntu dockerd[28173]: time="2017-04-21T17:52:45.801179559+05:30" level=warning msg="Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/a02a7b0ce64f9c238351cea1456c7d542ee9908b3a18bc8e
4aa12d7b88781abc: exec: \"auplink\": executable file not found in $PATH"
Apr 21 17:52:45 ubuntu azfile[28162]: time="2017-04-21T17:52:45+05:30" level=debug msg="request accepted" name=test1 operation=unmount
Apr 21 17:52:45 ubuntu azfile[28162]: time="2017-04-21T17:52:45+05:30" level=error msg="unmount failed: exit status 32\noutput=\"umount: /var/run/docker/volumedriver/azurefile/test1: not mounted\\n\"" name=test
1 operation=unmount
Apr 21 17:52:45 ubuntu dockerd[28173]: time="2017-04-21T17:52:45.829958160+05:30" level=warning msg="1b69f011fabb0f685fe5b38ea6c35376ffacf675f6578c7771f41f4668153026 cleanup: Failed to umount volumes: VolumeDri
ver.Unmount: unmount failed: exit status 32\noutput=\"umount: /var/run/docker/volumedriver/azurefile/test1: not mounted\\n\""
Apr 21 17:52:45 ubuntu dockerd[28173]: time="2017-04-21T17:52:45.830006784+05:30" level=error msg="Handler for POST /v1.24/containers/1b69f011fabb0f685fe5b38ea6c35376ffacf675f6578c7771f41f4668153026/start retur
ned error: VolumeDriver.Mount: mount failed: exit status 32\noutput=\"mount.cifs kernel mount options: ip=168.63.161.178,unc=\\\\\\\\glydata.file.core.windows.net\\\\test1b,vers=3.0,file_mode=0777,dir_mode=0777
,uid=0,gid=0,user=glydata,pass=********\\nmount error(11): Resource temporarily unavailable\\nRefer to the mount.cifs(8) manual page (e.g. man mount.cifs)\\n\""

The same set of operations runs successfully on Ubuntu 16.04 with the same docker and plugin versions

avegao commented 7 years ago

I have this issue in:

msftgits commented 6 years ago

This driver is no longer supported and will not be maintained moving forward. We recommend users use CloudStor for Docker native solutions.

Thanks for your contribution, but to reduce confusion, we are closing issues, pull requests, and marking the repo as 'Archive' for the time being.