I had installed the rclone docker plugin and used it for a couple of days, but it sudently stop working.
When trying to start my docker-compose stack I got this error :
ERROR: get build_remote-rclone: error while checking if volume "build_remote-rclone" exists in driver "rclone:latest": error looking up volume plugin rclone:latest: plugin rclone:latest found but disabled
So I tried re-enabling the plugin :
$ docker plugin enable rclone:latest
Error response from daemon: dial unix /run/docker/plugins/10585001507c0cf3af21c74472155d6958b569d232484270054be8b545c5662e/rclone.sock: connect: no such file or directory
and even tried to remove/reinstall the plugin :
XXX@docker:$ docker plugin rm rclone:latest
rclone:latest
XXX@docker:$ docker plugin install rclone/docker-volume-rclone:amd64 args="-v" --alias rclone --grant-all-permissions
amd64: Pulling from rclone/docker-volume-rclone
Digest: sha256:9db0559f0f32db36e42d9bc92358ef4013a06222b6c275215bc0fffedc3b3bd5
a84d98b8bb73: Complete
Error response from daemon: dial unix /run/docker/plugins/46be0fce963bfbbf4962ed34c5fe1a763b8e9bbca28501eef3c362941ce37936/rclone.sock: connect: no such file or directory
The only thig I did before I saw it
Run the command 'rclone version' and share the full output of the command.
docker plugin disable rclone # just to be sure, probably unneeded
docker plugin set rclone args="-vv" # bump up verbosity
docker plugin enable rclone # this will fail :( but also report in the log :)
The docker plugin log goes into the docker daemon log which is located OS dependent:
If you find documentation unclear, please take your time to help the community.
Please register / login on github, then
Open the document source by this link below
Click the top-right PEN icon.
Edit the document right in the browser to your taste.
Github will extract the difference and create a change request from your name.
We will later review your changes.
I can see from the log that the plugin had started up, restored its saved state and successfully finished mounting Google Drive at 18:23:01, but docker daemon failed to ping its health at 18:23:13, probably due to unexpected program abort.
Let's see what happens if you start the plugin cleanly.
Stop all compose jobs and docker containers using the remote
Stop the plugin with: docker plugin disable rclone
Remove saved plugin state on the host: sudo rm /var/lib/docker-plugins/rclone/cache/docker-plugin.state
Start the plugin again: docker plugin enable rclone
Check that plugin process is still running as seen from the host: ps -efa | grep "rclone serve docker"
Look in the docker daemon log: sudo cat /var/log/syslog | grep dockerd | less
Is everything OK yet? I hope so...
Start your mount-related containers / compose jobs now.
Check again if the plugin is still running?
If it works, just use it.
If the plugin will die, let's get rid of the docker for a moment and troubleshoot things simplistically:
Install rclone normally on the host as per this link: Install
It seem the first set of commands is working, I will keep an eye on it, It was fine too for at least a few hours last time, finger crossed.
As you suggested earlier, I might submit a documentation update proposal : I thought the uninstall/reinstall of the plugin would clear the state. I will submit an update with the state removal command as an addition in the troubleshooting section, with of course an accompagniing warning of its destructive side effect.
FWIW: I had a similar problem which appeared following a server reboot cycle and one of my containers using the rclone plugin failed to auto-start.
Here was the state of the plugin:
# docker plugin ls
ID NAME DESCRIPTION ENABLED
683199f0659d rclone:latest Rclone volume plugin for Docker false
I then attempted to enable:
# docker plugin enable rclone
Error response from daemon: dial unix /run/docker/plugins/683199f0659d741976aae8c5c08c624c7bc2704ace3bfe93e8ab693c95a7e9f3/rclone.sock: connect: no such file or directory
And then went through your steps above and the problem was resolved. Will keep an eye on things and report back if I have more details or repro steps.
Just to chime in and say I am facing similar problems here every time the docker daemon is restarted. It's definitely a frustrating occurrence, and I'd welcome any comments on how to resolve this issue.
Will keep an eye on things and report back if I have more details or repro steps.