[Bug 1214464] New: Unable to use --net=container on RHEL 6.6

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1214464

            Bug ID: 1214464
           Summary: Unable to use --net=container on RHEL 6.6
           Product: Fedora EPEL
           Version: el6
         Component: docker-io
          Severity: high
          Assignee: ichavero(a)redhat.com
          Reporter: pwebster(a)ca.ibm.com
        QA Contact: extras-qa(a)fedoraproject.org
                CC: adimania(a)gmail.com, admiller(a)redhat.com,
                    golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
                    ichavero(a)redhat.com, jchaloup(a)redhat.com,
                    jperrin(a)centos.org, lsm5(a)redhat.com,
                    mattdm(a)redhat.com, mgoldman(a)redhat.com,
                    miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
                    vbatts(a)redhat.com



Description of problem:

I can't use the --net=container option on a second container.  I get an error
and the container fails to start


Version-Release number of selected component (if applicable):
docker-io-1.4.1-3.el6.x86_64
RHEL 6.6
kernel-2.6.32-504.12.2.el6.x86_64

How reproducible: 100%


Steps to Reproduce:
1. Start up the first container
bash$ docker run -ti --name=target fedora /bin/bash

2. start up the second container in another xterm
bash$ docker run -ti --rm  --net=container:target  fedora /bin/bash


Actual results:

It spits out an error:
setup networking failed to setns current network namespace: invalid
argumentFATA[0002] Error response from daemon: Cannot start container
ac211304b75a4fca4839739e9769ded6e4fb61aa74bf9e862499aed09b12c3c6: setup
networking failed to setns current network namespace: invalid argument 


Expected results:
It just fires up the second container.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.