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: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected]
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.
_______________________________________________
golang mailing list
[email protected]
https://lists.fedoraproject.org/mailman/listinfo/golang
