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
- Copy your plugin'ified rclone config locally:
sudo cat /var/lib/docker-plugins/rclone/config/rclone.conf | cat > ./rclone.conf - Run ordinary rclone mount, mimicing the composed options:
rclone --config ./rclone.conf mount GDriveBackupNeoEncrypted: /tmp/test-mount-dir --poll-interval=0 --vfs-cache-mode=full --allow-other - Manually check the mount trying to behave like your compose'd program: list directories, copy files, etc
I wish your hunt were fruitful... Let me know below...