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?
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.
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