Ask Your Question

docker run --net test_net fails

asked 2019-12-10 07:21:10 -0500

madness31 gravatar image

Hello, I have used kuryr-libnetwork successfully for about a month, but unfortunately after full openstack reinstallation using juju I got error when trying to run docker container using kuryr-libnetwork directly on compute node. My juju bundle is the same like it used to be when it ran smoothly. Journalctl output is attached below

docker version 19.03.2

In /usr/local/libexec directory I have:

bridge iovisor midonet ovs tap unbound

  • Installed Zun manually (source: (
  • stable/stein version of Zun and Kuryr-libnetwork
  • Installed Kuryr-libnetwork manually (source: (
  • OS Ubuntu 18.04.3

In addition to, I can assure that I am able to create nova instances on nodes without errors

How to fully reproduce this error: First I am adding unit with nova-compute command and completely reinstall OS on compute node

1) juju add-unit nova-compute --to computei7-2.maas node

During step above nova-compute, ntp, neutron-openvswitch is installed on a completely fresh node

2) Installing docker from repo: (

3) Because I have already installed kuryr on controller ( ( I only install kuryr on compute using this guide: (

4) Creating docker network ( (

NETWORK ID NAME DRIVER SCOPE 4bdc0dd4bef0 bridge bridge local 71bbf6f23bdd host host local 94b75f0199ff none null local

docker network create --driver kuryr --ipam-driver kuryr \ --subnet --gateway= test_net

I get:


5) Finally, when I enter command "sudo docker run --net test_net cirros ifconfig"

I get:

docker: Error response from daemon: failed to create endpoint cocky_franklin on network test_net: NetworkDriver.CreateEndpoint: vif_type(binding_failed) is not supported. A binding script for this type can't be found. ERRO[0012] error waiting for container: context canceled

What I noticed is that when I try to create docker container within test_net network in a neutron-openvswitch logs I see this message:

INFO neutron.agent.common.ovs_lib [req-6bb7efbc-1cc7-4b0b-8819-a61f3ae1c175 - - - - -] Port a56f0e7f-e564-42ad-a752-0b32db37f919 not present in bridge br-int

Then, I check openstack port list using cli and get and do not see port with ID a56f0e7f-e564-42ad-a752-0b32db37f919

Howerver, when creating nova instance in neutron-openvswitch logs I see that it is port is being created and openstack port list command returns the same port ID as it was mentioned in neutron-openvswitch. Therefore, VM is created successfully

In neutron-openvswitch logs (on compute node) I see mentioned port a56f0e7f-e564-42ad-a752-0b32db37f919 from message:

INFO neutron.agent.common.ovs_lib [req-6bb7efbc-1cc7-4b0b-8819-a61f3ae1c175 - - - - -] Port a56f0e7f-e564-42ad-a752-0b32db37f919 not present in bridge br-int

It's ID differs from port ID's listed in openstack port list. In openstack port list I see that kuryr network port was created, but it ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2019-12-13 04:12:29 -0500

madness31 gravatar image

updated 2019-12-19 01:56:46 -0500

The only error from neutron-server I found is:

ERROR neutron.plugins.ml2.managers [req-d5bb3e97-40b3-4261-aaea-dadad88537bf b3e7880917484f6899d79bdfa9f91cfc 0043ed77cd8b453d897d499c457d2247 - 3a3cd562d047408fbf743d22f2f22eb8 3a3cd562d047408fbf743d22f2f22eb8] Failed to bind port 2661688f-90b2-4c72-bd32-58acaf1c9a2c on host computei7-2 for vnic_type normal using segments [{'id': '9f27f7c7-414c-4012-bed8-efe802ef1d31', 'network_type': 'gre', 'physical_network': None, 'segmentation_id': 43, 'network_id': 'cf5e6f43-2a0b-4015-8b8f-5fe8be335056'}]

Has anyone have any clue about this?


After all this time I finaly found out difference between error message shown node name and node name in "openstack compute service list" command. In error above neutron tries to bind port on host computei7-2 although when I type openstack compute service list I see only computei7-2.maas

What I did was:

1) Changed /etc/nova/nova.conf file host line in compute node instead of computei7-2.maas to computei7

2) Changed /etc/nova/neutron.conf file host line in compute node instead of computei7-2.maas to computei7

3) Reboot compute node

4) In openstack controller removed compute service with a name ending .maas:

openstack compute service delete $ID

5) Rebooted a node

After all these procedures I am able to launch docker container on compute node with command "docker run --net test_net cirros ifconfig"

Someone with more karma points please mark this answer as answered!

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2019-12-10 07:21:10 -0500

Seen: 136 times

Last updated: Dec 19 '19