-
Notifications
You must be signed in to change notification settings - Fork 667
run weave on remote docker #312
Comments
It should be.
Would be great if you took a stab at getting this to work.
|
I was bored... The Dockerfile
will construct a
I haven't done much testing with this, but so far everything appears to work just fine. Remotely too, though one obviously needs to get the zettio/weaveimg into the remote docker by either building it there or publishing it to the dockerhub or |
Awesome, thanks.
|
I am re-opening this since conceivably this is a feature weave should support more directly. E.g. when DOCKER_HOST is set, the weave script could automatically delegate the command to that host via the mechanism described above. Or we could go one step further and always do that, i.e. |
Some thoughts on the image we need to construct for this...
|
I've just come across comments by @progrium pointing to Alpine Linux - might this be a useful base image because it has a more complete package manager? (to fetch all the little bits and pieces) |
As an approximation,
gives an image
Adding the proxy is another 6MB or so; the docker client is another 14MB. The docker exe can be bind-mounted from the host, but another idea struck me: perhaps the script can be split into those parts that deal with dockerating (to live in the "remote" script), and those parts that enact networking config (to live in the inner, container-borne script). |
https://github.com/squaremo/weave/tree/weave_in_weavetools is a PoC of putting the weave script in a container and having a "thin client" script that drives it. It's enough to be able to run |
Notes on using busybox:
|
Does that indicate our use of
What's the problem? |
Or perhaps your notes were in relation to alpine. Btw, conflating build and runtime in one image, and consequently shipping an image that contains a package manager and init.d, is a dreadful idea. Though I am prepared to hold my nose on that one. |
I, too, prefer separate build and runtime images when you need to build. On Tue, Jan 27, 2015 at 11:33 AM, rade notifications@github.com wrote:
Jeff Lindsay |
The "no escaping of parens, plus, etc." is the extended regex syntax. What led to the conclusion that basic regular expressions are not sufficient? If there are sed scripts where we go outside of BREs, it is probably best to try to adapt them to conform before switching to EREs. |
Right yes, I wasn't being very scientific, by which I mean accurate.
Sure. GNU sed supports |
Move weave script into tools image with its deps and thus enable weaving on a remote docker Closes #312.
Say I want to run weave on two remote hosts that I'm connected to via there docker daemon, could I invoke the weave router on them via docker (without running commands via SSH)
something like
DOCKER_HOST=tcp://someremote:2375 docker run weaveimg weave launch
DOCKER_HOST=tcp://otherremote:2375 docker run weaveimg weave launch someremote
I assume if it can work at all, i would have to user --privileged and -host and maybe other things ..
In others words can weave itself be run within a container ?
Is that possible at all ? is that documented anywhere ?
Thank you.
The text was updated successfully, but these errors were encountered: