DEBUG:__main__: Attaching container 3-node_cEOS-1 interface eth1 to its link
DEBUG:__main__: Connecting veth-type link to 3-node_cEOS-1
DEBUG:__main__:Connecting 3-node_net-1-a to 3-node_cEOS-1
DEBUG:__main__:Create an interface for container 3-node_cEOS-1: {'ifname': 'eth1', 'stats': None, 'protinfo': None, 'map': None, 'linkinfo': None, 'stats64': None, 'af_spec': None, 'net_ns_fd': 30, 'event': None, 'flags': 4099, '-ports': set(), '+ports': set(), '-ipaddr': set(), '+ipaddr': set(), '-vlans': set(), '+vlans': set()}
Traceback (most recent call last):
File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 840, in <module>
main()
File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 775, in main
started = [device.start() == 0 for (name, device) in devices.items()]
File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 775, in <listcomp>
started = [device.start() == 0 for (name, device) in devices.items()]
File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 354, in start
self._attach()
File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 371, in _attach
link.connect(self, interface)
File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 659, in connect
self.network.connect(device, interface)
File "/home/wade/ceos/docker-topo/testdir/bin/docker-topo", line 601, in connect
with IPDB(nl=NetNS(ns_name)) as ns:
File "/home/wade/ceos/docker-topo/testdir/lib/python3.7/site-packages/pyroute2/netns/nslink.py", line 170, in __init__
super(NetNS, self).__init__(trnsp_in, trnsp_out)
File "/home/wade/ceos/docker-topo/testdir/lib/python3.7/site-packages/pyroute2/iproute/linux.py", line 127, in __init__
super(RTNL_API, self).__init__(*argv, **kwarg)
File "/home/wade/ceos/docker-topo/testdir/lib/python3.7/site-packages/pyroute2/remote/__init__.py", line 200, in __init__
raise init['error']
OSError: [Errno 22] failed to open netns: 'e5df19bfe142'
I'm using the
topo-extra-files/examples/v2/3-node.ymlsample file. The host is Fedora 18 with a 4.9.76 kernel. I can use the bridge driver to get around this issue for now, it seems.Here's the last part of
docker-topo --debug --create topo-extra-files/examples/v2/3-node.ymlFull log: debug.txt
I also confirmed that
e5df19bfe142existed as/var/run/docker/netns/e5df19bfe142