veth pair cannot be created as vif_type is invalid

[Marco Chiappero]

When starting a new container with "driver = kuryr.lib.binding.drivers.veth" and Kuryr IPAM, docker fails with the following message:

docker: Error response from daemon: NetworkDriver.Join: vif_type(binding_failed) is not supported. A binding script for this type can't be found.

It seems that the value from port.get(VIF_TYPE_KEY) on a newly created port is by default set to "binding_failed", so the veth creation will succeed but binding won't, resulting in a failed join.

To reproduce:
- start kuryr with the above setting
- create a docker network, e.g.:
docker network create --driver=kuryr --ipam-driver=kuryr --subnet 10.10.0.0/16 --gateway=10.10.0.1 -o neutron.net.uuid=bf2589ee-8a9a-4f3e-a203-42e0b3e91770 private_net

- start a new container using the above network, e.g.:
docker run -it --rm --net=private_net alpine /bin/sh

[Dongcan Ye (hellochosen)]

Thanks for bug report, would you mind me to take a look at this problem?

[Marco Chiappero (mchiappe)]

Yes please, I'm quite busy at the moment, but I should be able to do testing.

[Liping Mao (limao)]

Hi Marco,

Can you help to double chek the bindir seting in /etc/kuryr/kuryr.conf?
make sure the kuryr bind script is installed in proper dir.

In my environment, I using bindir = /opt/stack/kuryr/usr/libexec/kuryr
and scripts are in /opt/stack/kuryr/usr/libexec/kuryr.

Thanks.
Regards,
Liping Mao