Closed btyler97 closed 9 years ago
Hi @btyler97
According to Docker doc, the plugin spec file can only be put in /etc/docker/plugins
or /usr/lib/docker/plugins
. Probably /usr/lib/docker/plugins
would fits your need better?
@yasker, thank you, but aren't the only locations available on the persistent partition under /var/lib/docker
and /var/lib/boot2docker
? The point is, if I define that spec under /usr/lib/docker/plugins
or /etc/docker/plugins
it would gets wiped on a docker-machine restart
.
It's looking like the best option would be to write a /var/lib/boot2docker/bootlocal.sh
script to install, configure and startup the convoy plugin. Would you agree?
Yeah, I think that's the best bet.
The file content for convoy.spec remain unchanged(as long as you don't change Convoy sock path) and can be easily recreated from script.
Great, thank you. I tried that and it seems to have done what i need. Cheers!
I'm working on a POC for a development environment utilizing Rancher, Docker Machine and Convoy for persistent storage. Ultimately, I'll probably add (more permanent) hosts through some other provider (eg: OpenStack or AWS), but for the time being, I'm stuck with Docker Machine and the VirtualBox driver.
The problem with the current installation and configuration steps is that the recommendations are to place things in ephemeral locations on the Docker host (ex: /usr/local/bin/, /etc/docker/plugins/). I can work around the placement of volumes, binaries and startup scripts, but the one that has me stumped is the /etc/docker/plugins location where it seems Docker expects the Convoy socket definition.
Do you have a recommended setup for running Convoy in a Docker Machine/VirtualBox environment?