quick fix with:
iptables -A INPUT -i docker0 -m comment --comment "000 accept all through docker0" -j ACCEPT
This should be part of build host deployment scripts. I will move this to low priority 6.0 and we can add a quick test that does something like this:
docker run --rm -i -t fuel/centos curl http://172.17.41.1: $(RANDOM_PORT)/os/x86_64/ || (echo "ERROR: Docker container communication is blocked by host firewall!!!" && false)
The command above will fail make based on network communication and make the error obvious. It will add roughly 3 seconds to deployment time.
quick fix with:
iptables -A INPUT -i docker0 -m comment --comment "000 accept all through docker0" -j ACCEPT
This should be part of build host deployment scripts. I will move this to low priority 6.0 and we can add a quick test that does something like this: 172.17. 41.1: $(RANDOM_ PORT)/os/ x86_64/ || (echo "ERROR: Docker container communication is blocked by host firewall!!!" && false)
docker run --rm -i -t fuel/centos curl http://
The command above will fail make based on network communication and make the error obvious. It will add roughly 3 seconds to deployment time.