OVN/OVS driver not recognized by docker about ovn-docker HOT 6 OPEN

When I type
docker network create -d openvswitch --subnet=172.19.1.0/24 ovs-br1
It shows
Error response from daemon: legacy plugin: plugin not found

I have tested till Docker 1.13. Based on the error, it looks like something has changed with v17.03.0-ce in terms of place where it looks for the plugin. I will spend some time.

from ovn-docker.

I have tested till Docker 1.13. Based on the error, it looks like something has changed with v17.03.0-ce in terms of place where it looks for the plugin. I will spend some time.

I've rolled back my docker to v1.12.1 and the bug is still there, so it has nothing to do with Docker version.
Since there's no error message when I type ovn-docker-overlay-driver --detach, I guess it just quits halfway. I'm trying to figure it out.
Any idea of why? for example, iptables, port, prequistion, whatever...

from ovn-docker.

I've rolled back my docker to v1.12.1 and the bug is still there, so it has nothing to do with Docker version.

When you run ovn-docker-overlay-driver (without --detach), does it print any errors?

from ovn-docker.

FYI, I ran the vagrant that comes with this repo. And I did not see any problems. It used docker 17.03.1-ce. You can quickly look at the scripts the vagrant uses to run consul, docker and ovn.

i.e look at https://github.com/shettyg/ovn-docker/blob/master/vagrant_overlay/Vagrantfile to all the scripts that it invokes and then see the individual simple scripts.

You can always come to IRC (freenode). I am there in the #openvswitch channel as "shettyg". You can ping me if you need live debugging.

from ovn-docker.

i.e look at https://github.com/shettyg/ovn-docker/blob/master/vagrant_overlay/Vagrantfile to all the scripts that it invokes and then see the individual simple scripts.

Thanks for the scripts. I've made a mistake when setting Consul cluster. Now everything works fine ^_^

I notice that after running creating a ovn-docker network and starting a container attached to the network, docker automatically creates docker_gwbridge network. It seems this bridge functions similarly to docker0.

Does it mean that if a container wish to communication with the outside ( e.g other servers in a LAN ), docker_gwbridge is the only gateway? Since we've created a switch when creating ovn-docker network, is it possible to make the switch function as a gateway?

Thank you for your time.

from ovn-docker.

Does it mean that if a container wish to communication with the outside ( e.g other servers in a LAN ), docker_gwbridge is the only gateway? Since we've created a switch when creating ovn-docker network, is it possible to make the switch function as a gateway?

OVN has multiple options to connect to outside world. If you are running on baremetal, you can connect your switch to vlans via OVN switch. You can also use OVN routers to connect. But the docker plugin does not do any of that. The kubernetes integration uses OVN router to connect to outside world - https://github.com/openvswitch/ovn-kubernetes/

from ovn-docker.