Reputation
Top tag
Next privilege 50 Rep.
Comment everywhere
Badges
3
Impact
~2k people reached

  • 0 posts edited
  • 0 helpful flags
  • 0 votes cast
Jun
8
comment Routing from docker containers using a different physical network interface and default gateway
Unfortunately this did not work. My complete process was to run: ip rule add from 172.17.0.0/16 table docker ip route add default via 192.168.1.2 dev eth1 table docker ip route flush cache iptables -t nat -D POSTROUTING 1 iptables -t nat -A POSTROUTING -s 172.17.0.0/16 -j SNAT --to-source 192.168.1.2 /etc/init.d/docker restart. Then I tried to run a ping out and a traceroute from a container, and was unable to reach anything.
Jun
5
comment Routing from docker containers using a different physical network interface and default gateway
Here is a link back to the Github Issue: github.com/docker/docker/issues/13762
Jun
5
comment Routing from docker containers using a different physical network interface and default gateway
@Matt I thank you for your suggestions on this. From what I've read pipework requires additional commands after a container is started to get it access to the correct gateway which seems like a security vulnerability. It was originally created to connect containers together across multiple hosts, which really isn't my goal here. As for the Docker advanced networking docs, I'll take a look again, but it hasn't been helpful in this situation so far (I had read it before posting here). I am going to post a link to this post on the docker Github Issues page and see how it goes from there.
Jun
4
comment Routing from docker containers using a different physical network interface and default gateway
Unfortunately this did not work. My containers were still routing out to the same default gateway as the host. Here's what I ran: ip rule add from 172.17.0.0/16 table docker ip route add default via 192.168.1.2 dev eth1 table docker ip route flush cache /etc/init.d/docker restart From in the container I ran a traceroute and the first hop was 10.1.1.1 when it should have been 192.168.1.1
Jun
4
comment Routing from docker containers using a different physical network interface and default gateway
Thanks for your comment. So that would change my approach for routing out of a specific interface then, correct? Do you know how I could go about accomplishing this? As it stands Docker seems to just use the default gateway of the host system, and this isn't the desired behavior. I want all things Docker to route out of a specific interface.
Jun
4
asked Routing from docker containers using a different physical network interface and default gateway
Apr
11
awarded  Popular Question
Jul
13
awarded  Autobiographer
May
17
comment Monitoring an ISC DHCP Failover Status Using Nagios
I considered check_dhcp, but check_dhcp still will only provide circumstantial evidence toward the case of a failover state being active. In other words, it's possible a server will/will not lease to check_dhcp for reasons other than a failover state. I'm looking for more direct evidence of the failover state. Thank you for the links to BPI and Shinken, however.
May
16
awarded  Student
May
16
asked Monitoring an ISC DHCP Failover Status Using Nagios