-
Notifications
You must be signed in to change notification settings - Fork 92
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
can run under boot2docker? #5
Comments
sorry, I just spotted the OSX section at the bottom of the front page readme :) |
ok my intuition was wrong, this works fine:
but I'm having trouble with the rest of it... |
"Open file My attempt to follow this under boot2docker is:
then I run the dnsdock container as instructed then "In your Vagrantfile add the following to let your virtual machine accept packets for other IPs" ...boot2docker isn't backed by Vagrant any more so I went to the VirtualBox GUI and edited the network settings for for this part:
...I assumed this is running on my OSX host. I got the IP address from added a file (on OSX host again) then |
I'm not sure how to test it's working, but this output doesn't look like yours so I think it isn't:
|
I tried boot2docker and everything seemed to work fine for me. I didn't even need to set the In boot2docker profile the correct format for daemon arguments seems to be If you make a file How to debug:
|
this morning I tried to undo everything I did above and try a different approach coming back to it... my |
I had changed the promiscuity of the vm back to 'deny', removed the route etc |
I upgraded to 1.3.1 and was hit by boot2docker/boot2docker#606 so make sure you can ping to the Is the route visible with Other than that everything worked fine in |
I can ping the I can |
Don't know then, sorry. Must be some differences in virtualbox or osx(I'm using yosemite). Does |
ah thanks, the problem is I had deleted the route and not added it back again |
I'd love to see is some discussion/instruction of what needs to be done different when running under boot2docker, I'm assuming the part where you share the host's
/var/run/docker.sock
as a volume isn't going to work.I found some instructions here:
http://www.devopslife.com/2014/08/08/docker-boot2docker-and-dns-resolution-of-containers.html
It's aimed at skydock but the first part would be the same I think. However in comments people say this no longer works for docker 1.3.1 due to some change
I'd also love to see an example fig.yml for running dnsdock as a service under fig
The text was updated successfully, but these errors were encountered: