New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: access to 10/8 CIDR despite no if with such IP? #431
Comments
The above is quite advanced usage of weave. If you are new to weave I strongly recommend you follow our intro in the README to become familiar with it. |
I've followed that intro, too and yes, the output that you've written should come, comes. |
As to your specific question, I suspect the answer can be found in our docs on application isolation, in particular this bit
|
I see! Let me try it! |
That didn't work. I have this in
Doing a Doing a Pinging 10.1.0.2 (started above) from the container started with
It might be that the docker daemon in boot2docker isn't reading the /var/lib-file -- but instead from somewhere else entirely. boot2docker doesn't have the brctl command - perhaps that matters? Doing a |
/etc/default/docker didn't work either. New machines are still not getting the right CIDR. |
So it seems that boot2docker is a very strange kind of linux, I'm giving up on it and using the coreos boxes that I'll use in prod instead. They seem differently configured. |
Is there anywhere I can get help faster than this? It'll take many days to learn at this speed. |
I'm going to try Deis and Flannel instead. |
You could try (have tried) our IRC channel #weavenetwork on freenode. |
I'm experimenting with weave, aiming to use it together with consul to make our docker deployment across a couple of hosts a cluster with failover services running (registrator + consult + weave).
So far I'm in the 'learning' stage, so I have a question, I was hoping you might be able to answer.
I have run 'weave launch' and basically followed all steps in what seems to be the guide to weave https://sttts.github.io/docker/weave/mesos/2015/01/22/weave.html.
I haven't been able to:
docker run
is usedHowever, this is the state:
And when doing a
docker exec
insideeventstore.0
, which was started withdocker run
as opposed toweave run
it can still ping 10.0.0.1 -- how does with work out?PS: it is not my fault that docker named The Registrator "boring torvalds" 🎱
The text was updated successfully, but these errors were encountered: