Closed djeeg closed 6 years ago
@djeeg we ran into this issue as well, so we had to abandon containerizing anything that needed persistent storage unfortunately. It appeared to be an issue where after a certain period of idle time, the smb connection would go stale/timeout, which the driver doesn't handle well, and results in the behavior you are seeing. Hopefully someone picks this up and irons it out, as it would open a ton of use cases for us.
It happens to me as well but without docker stuff, just mounting my File Storage into my linux VM. Any news on the issue?
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.
Hi, wondering if anyone has seen a problem like this
After a while my swarm node become unstable, think I have traced it back to a problem with azure volume driver
Try this
Doesnt return, must break out of it
https://github.com/Azure/azurefile-dockervolumedriver/releases/download/v0.5.1/azurefile-dockervolumedriver
Checked a few other posts, my settings looks normal
systemctl status
systemctl status azurefile-dockervolumedriver
journalctl -fu azurefile-dockervolumedriver
cat /etc/systemd/system/azurefile-dockervolumedriver.servicenode
Remove the volumes manually
Still cant list volumes
Then restart docker and driver
I can now list local volumes again