CODEWITHSUNDEEP
dockerdocker-network
Marcello DeSales
Marcello DeSales

Reputation: 22358

Docker Networking Disabled: WARNING: IPv4 forwarding is disabled. Networking will not work

Containers in a host "suddenly" loses connection to outside-world containers. However, some hosts were refreshed and suddenly we had the following situation:

  1. The host can communicate with other hosts.
  2. Containers running in the host cannot communicate with other hosts.

Here's an example:

[root@pprdespap322 deploy]# ping ci.docker.company.net
PING pprdespap324.corp.company.net (10.137.55.22) 56(84) bytes of data.
64 bytes from pprdespap324.corp.company.net (10.137.55.22): icmp_seq=1 ttl=64 time=0.282 ms
64 bytes from pprdespap324.corp.company.net (10.137.55.22): icmp_seq=2 ttl=64 time=0.341 ms
^C
--- pprdespap324.corp.company.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.282/0.311/0.341/0.034 ms

Now, from the container itself, we cannot ping the same host:

[root@pprdespap322 deploy]# docker run -ti quay.io/coreos/registry ping ci.docker.company.net
WARNING: IPv4 forwarding is disabled. Networking will not work.
ping: unknown host ci.docker.company.net

The first time I saw this warning was in the initial versions of Docker... Having Docker 1.9.1 and 1.10.3, How to solve this problem?

Upvotes: 183

Views: 185783

Answers (5)

Nada Magdy
Nada Magdy

Reputation: 41

What worked for me:

  1. Edit /etc/sysctl.conf and ensure the following line is present / uncommented:
net.ipv4.ip_forward=1

  1. Run sudo sysctl -p so changes take effect.

  2. Restart the affected container:

docker restart [container_name/id]

Upvotes: 4

DmitrySandalov
DmitrySandalov

Reputation: 4109

Try restarting Docker service.

E.g. for Ubuntu:

$ sudo systemctl restart docker

Upvotes: 114

Cristiano Kubiaki
Cristiano Kubiaki

Reputation: 51

Solved my issue restarting the network.

systemctl restart network

Upvotes: 5

Ganesh Chandrasekaran
Ganesh Chandrasekaran

Reputation: 1936

Try adding --network=host along with docker run command to fix this.

https://medium.com/@gchandra/docker-ipv4-forwarding-is-disabled-8499ce59231e

Upvotes: 28

Marcello DeSales
Marcello DeSales

Reputation: 22358

I reviewed http://chrisgilmerproj.github.io/ubuntu/network/docker/2013/09/05/ipv4-forwarding-and-docker.html and it helped me solving the problem on the host.

I added the following to /etc/sysctl.conf: 

net.ipv4.ip_forward=1

I then restarted the network service and validated the setting:

[root@pprdespap322 deploy]#  systemctl restart network
[root@pprdespap322 deploy]# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1
[root@pprdespap322 deploy]# docker run -ti quay.io/coreos/registry ping ci.docker.company.net
PING pprdespap324.corp.company.net (10.137.55.22) 56(84) bytes of data.
64 bytes from pprdespap324.corp.company.net (10.137.55.22): icmp_seq=1 ttl=63 time=0.329 ms
64 bytes from pprdespap324.corp.company.net (10.137.55.22): icmp_seq=2 ttl=63 time=0.306 ms
^C
--- pprdespap324.corp.company.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.306/0.317/0.329/0.021 ms

All containers now can communicate with outside world containers!

Upvotes: 259

Related Questions