[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: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail], [e-mail],
                    [e-mail]

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:

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

[Red Hat Bugzilla]

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

--- Comment #1 from Paul Webster  ---
Created attachment 1018016
  --> https://bugzilla.redhat.com/attachment.cgi?id=1018016&action=edit
Failure logs when docker can't attach to the second container

This log occurs during the second container run command:
First container:
bash-4.1$ docker run -ti --name=target ubuntu /bin/bash
root@45edefd42404:/#

Second container:
bash-4.1$  docker run -ti --rm --net=container:target ubuntu /bin/bash
setup networking failed to setns current network namespace: invalid
argumentFATA[0002] Error response from daemon: Cannot start container
ba28e4f14f4b3c2d7b94aa4b0cca8f5b70e6b354842818fe77b31885acc77461: setup
networking failed to setns current network namespace: invalid argument

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

[Red Hat Bugzilla]

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

--- Comment #2 from Paul Webster  ---
Created attachment 1018436
  --> https://bugzilla.redhat.com/attachment.cgi?id=1018436&action=edit
Failure log with docker-io 1.5.0

I took an update to docker-io-1.5.0-1.el6.x86_64 yesterday but it still fails
with the invalid argument message:

bash-4.1$ docker run -ti --name=target ubuntu /bin/bash
root@e90fa60b6c8e:/#

bash-4.1$ docker run -ti --rm --net=container:target ubuntu /bin/bash
FATA[0001] Error response from daemon: Cannot start container
2502130ff859150aa7f9cd28b0e50f495df1f6ecf9c14ce8abf606a2d806df25: invalid
argument

I've attached the new failure log from docker -d -D.

PW

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

[Red Hat Bugzilla]

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

Daniel Walsh  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |[e-mail]
           Assignee|[e-mail]         |[e-mail]

--- Comment #3 from Daniel Walsh  ---
Sally can you check if this fails on current docker?  docker-1.6.2 or
docker-1.7

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

[Red Hat Bugzilla]

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

--- Comment #4 from Sally  ---
1st term:
$ docker run -ti --name=target fedora /bin/bash
[root@b2d4337ae33f /]#

2nd term:
$ docker run -ti --rm  --net=container:target  fedora /bin/bash
[root@b2d4337ae33f /]#

No errors, running docker 1.8.0-dev

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

[Red Hat Bugzilla]

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

Lokesh Mandvekar  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail]             |

--- Comment #5 from Sally  ---
Since docker 1.7 won't run on RHEL/Centos 6.6 (needs kernel upgrade)without a
LOT of tweeking, should we close this bug? I verified the above running on
Fedora 21.

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

[Red Hat Bugzilla]

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

Lokesh Mandvekar  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #6 from Lokesh Mandvekar  ---
I think this would be a 'CLOSED CANTFIX' :( see:
https://github.com/docker/docker/issues/14365

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

[Red Hat Bugzilla]

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

--- Comment #7 from Paul Webster  ---
Doesn't the github issue state that docker 1.7.x should work on RHEL6?  How is
it possible to pick that up?

PW

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

[Red Hat Bugzilla]

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

--- Comment #8 from Paul Webster  ---
Even docker 1.6.x would be an improvement.

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

[Red Hat Bugzilla]

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

Lokesh Mandvekar  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #9 from Lokesh Mandvekar  ---
Paul, RE: 1.6.x could you please try running this build:
https://kojipkgs.fedoraproject.org//packages/docker-io/1.6.2/3.el6/x86_64/do...
it's yet to land in the testing repos.

Also copying wolfy, who built the latest update, but not sure if he's noticed
this bug.

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

[Red Hat Bugzilla]

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

--- Comment #10 from Sally  ---
Lokesh, this works for me.  Thanks.  Also the output from comment 4 is
confirmed running:

docker 1.6.2  on Centos 6.6, kernel 2.6.32-504.23.4.el6.x86_64

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

[Red Hat Bugzilla]

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

--- Comment #11 from manuel wolfshant  ---
If the package seems fine to you, please wait for it to land in epel-testing
and then pay a visit to
https://admin.fedoraproject.org/updates/docker-io-1.6.2-3.el6 and provide
karma. TIA.

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

[Red Hat Bugzilla]

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

--- Comment #12 from Paul Webster  ---
(In reply to manuel wolfshant from comment #11)
> If the package seems fine to you, please wait for it to land in epel-testing
> and then pay a visit to
> https://admin.fedoraproject.org/updates/docker-io-1.6.2-3.el6 and provide
> karma. TIA.

I'll keep my eye out for it.

Thanks,
Paul

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

[Red Hat Bugzilla]

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

--- Comment #13 from Paul Webster  ---
This still doesn't work for me:
bash-4.1$ docker run -ti --name=target ubuntu /bin/bash
root@191130b5ddb8:/#

bash-4.1$ docker run -ti --rm --net=container:target ubuntu /bin/bash
FATA[0002] Error response from daemon: Cannot start container
37ae928a6bb99941bc3c0ef02276fb5c5d93b71343d44604f3a513262fbf3523: [8] System
error: invalid argument

kernel-2.6.32-504.23.4.el6.x86_64
docker-io-1.6.2-3.el6.x86_64

What other packages should I look to so I can verify their version numbers?

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

[Red Hat Bugzilla]

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

--- Comment #14 from Sally  ---
I'm running docker (Docker version 1.6.2, build 7c8fca2/1.6.2) 
installed on Centos 6.6 kernel: 2.6.32-504.23.4.el6.x86_64

First, I removed current Docker with:
$ yum list installed | grep docker
$ sudo yum -y remove <output from above>

I then installed Docker by using the build from Comment 9:

$ curl -O -sSL
https://kojipkgs.fedoraproject.org//packages/docker-io/1.6.2/3.el6/x86_64/do...

$ sudo yum localinstall --nogpgcheck docker-io-1.6.2-3.el6.x86_64.rpm

$ sudo service docker start

Then the cmds in Comment 13 run with no errors.

Hopefully this will work for you (see Comment 11).

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

[Red Hat Bugzilla]

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

--- Comment #15 from Paul Webster  ---
I still receive my error using the new docker package.  AFAIK I have an up to
date RHEL 6.6 image.  If there are any other packages whose version I can
check, please let me know.

kernel-2.6.32-504.23.4.el6.x86_64
docker-io-1.6.2-3.el6.x86_64
iproute-2.6.32-33.el6_6.x86_64

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

[Red Hat Bugzilla]

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

--- Comment #16 from manuel wolfshant  ---
(In reply to Paul Webster from comment #15)
> kernel-2.6.32-504.23.4.el6.x86_64
> docker-io-1.6.2-3.el6.x86_64
> iproute-2.6.32-33.el6_6.x86_64

All those are the most current. No idea about docker though. Lokesh ?

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

[Red Hat Bugzilla]

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

--- Comment #17 from Daniel Walsh  ---
I think this might be a problem with the rhel6 kernel not supporting something
docker is trying to do.

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

[Red Hat Bugzilla]

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

Daniel Walsh  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |CLOSED
         Resolution|---                         |WONTFIX
        Last Closed|                            |2015-08-20 23:25:30