https://bugzilla.redhat.com/show_bug.cgi?id=1026045
Bug ID: 1026045
Summary: enable container networking (temporary solution for dm
branch)
Product: Fedora
Version: rawhide
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
vbatts(a)redhat.com
Description of problem: container networking doesn't work by default
Version-Release number of selected component (if applicable): docker-io 0.7.dm
How reproducible: iiuc, this occurs in the presence of a firewall (Matt,
correct me if I'm wrong)
Steps to Reproduce:
1. install docker-io, and enter a container
2. try any command which requires network connections (ping, yum, ssh)
3. feel the pain
Josh has a pull request against the master branch here:
https://github.com/dotcloud/docker/pull/2527 which is a little painful to apply
against dm, so I used the ACCEPT rules in his patch in the docker.service file,
so the current file looks like:
------------docker.service-------------------
[Unit]
Description=Docker container management daemon
[Service]
Type=simple
ExecStartPre=/usr/sbin/sysctl -w net.ipv4.ip_forward=1
net.ipv6.conf.all.forwarding=1
ExecStartPre=iptables -I FORWARD -o docker0 -m conntrack --ctstate
RELATED,ESTABLISHED -j ACCEPT
ExecStartPre=iptables -l FORWARD -i docker0 ! -o docker0 -j ACCEPT
ExecStart=/usr/bin/docker -d
Restart=on-failure
[Install]
WantedBy=multi-user.target
------------docker.service-------------------
this seems to solve the problem for now, and if I'm not mistaken, isn't
harmful.
Comments?
--
You are receiving this mail because:
You are on the CC list for the bug.