-
Notifications
You must be signed in to change notification settings - Fork 6
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
LXC cannot reach the Internets #3
Comments
I got a fix. An ugly, ugly fix. Once your test-lab is up:
(or via binstubs, or however you roll). Then on that box:
and then to make sure this survives a reboot:
and now your containers can reach the outside world. I'm sure this should be baked into the cuke-chef provisioning somehow, but I know not where. |
The iptables commands are fully cargo-culted from various howtos, there may well be better ways to achieve the same result. |
Also, this is on Vagrant/VirtualBox. Maybe this all works fine on AWS. |
Thanks John Frum. I am confounded why this cult knowledge is so obscure. |
Never bet against me having done something wrong, but the containers don't seem to be able to get the wider internet, and so cannot retrieve any packages. Using the devop-test-1 container from this repo:
I guess that gateway (the test-lab) should be forwarding packets. Have I done something dumb?
S
The text was updated successfully, but these errors were encountered: