Similar thing happened, like in this
topic, and i could not even enable the rclone plugin due to error
Error response from daemon: dial unix /run/docker/plugins/.../rclone.sock: connect: no such file or directory and it was solved by
sudo rm /var/lib/docker-plugins/rclone/cache/docker-plugin.state like written in
this reply but the volumes needed to be re-created (luckily i had docker-compose ymls for all my things, so it was easy).
Is there a way to avoid problems like these in the future?
- os/version: ubuntu 20.04 (64 bit)
- os/kernel: 5.4.0-144-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.19.4
- go/linking: static
- go/tags: none
Buy a UPS to avoid power failures? Things tend to go bad if you remove power from a computer.
March 29, 2023, 1:08pm
A UPS is a good idea.
I wonder why the
File is so delicate. What is in it? What is in it when the plugin no longer works? Maybe we can help with that, though that sounds like it is a file docker writes rather than rclone.
All of the volume settings that are use rclone is in that file for example:
But before the deletion of this file, the volumes are gone already, so not this is what causes the deletion.
March 29, 2023, 2:11pm
I wonder from your error message
It can't seem to find the socket file - maybe that is just a symptom of rclone not starting up properly, I don't know.
no it is not starting, and cant be started as plugin, until that file is deleted
March 30, 2023, 7:42am
Should the plugin be deleting this file if it can detect it is stale?
I know nothing about how docker plugins work and the developer who made the rclone one isn't available unfortunately so I'm looking for help to solve this
Neither i know if its docker, or plugin responsibility to cleanup
May 2, 2023, 6:44pm
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.