You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, many thanks for the great idea so far. Iam loving btrfs and doing scheduled stuff like snapshotting, syncing, etc. directly with docker is a really great addition.
After installing the plugin like described there is no socket inside /var/run/docker/plugins/. The plugin created a socket at some subpath, e.x. /var/run/docker/plugins/4537bd7d3e863809942031a9f87c54c2f5c38922d4286c1d9ebbcea3d6df4f22/btrfs.sock.
I could bring the plugin to work by creating a symbolic link ln -s /4537bd7d3e863809942031a9f87c54c2f5c38922d4286c1d9ebbcea3d6df4f22/btrfs.sock /var/run/docker/plugins/btrfs.sock and manually starting the daemon buttervolume run.
Running buttervolume run printed the following:
Starting scheduler job every 60s
Listening to requests...
Serving on http://unix:/run/docker/plugins/btrfs.sock
INFO:root:New scheduler job at 2018-06-06 12:22:20.475458
The text was updated successfully, but these errors were encountered:
Hi, I've just released version 3.5 with a more explicit doc about the socket and the difference between running butterbolume as a new-style plugin or running it manually. Closing this issue, you can reopen if you still have some suggestion. Thanks!
Hi, many thanks for the great idea so far. Iam loving btrfs and doing scheduled stuff like snapshotting, syncing, etc. directly with docker is a really great addition.
After installing the plugin like described there is no socket inside
/var/run/docker/plugins/
. The plugin created a socket at some subpath, e.x./var/run/docker/plugins/4537bd7d3e863809942031a9f87c54c2f5c38922d4286c1d9ebbcea3d6df4f22/btrfs.sock
.I could bring the plugin to work by creating a symbolic link
ln -s /4537bd7d3e863809942031a9f87c54c2f5c38922d4286c1d9ebbcea3d6df4f22/btrfs.sock /var/run/docker/plugins/btrfs.sock
and manually starting the daemonbuttervolume run
.Running
buttervolume run
printed the following:The text was updated successfully, but these errors were encountered: