Enabled network plugin fails to get registered after daemon restart #29471
Description
Description
Network plugins and drivers get registered to a DriverRegistry in libnetworK, which will be used for subsequent operations. But after a daemon restart, previously installed network plugin fails to get registered to the drvRegistry and hence is not usable during subsequent network creation.
Steps to reproduce the issue:
Install network-plugin and create a network.
$ sudo docker plugin install tiborvass/test-docker-netplugin
Plugin "tiborvass/test-docker-netplugin" is requesting the following privileges:
- network: [host]
Do you grant the above permissions? [y/N] y
tiborvass/test-docker-netplugin
$ sudo docker network create -d tiborvass/test-docker-netplugin:latest testnet2
16262841d23a96d287c58b4569d2ba3f6205d29f7eeff5fa658f882a32e89111
Restart the daemon, make sure the plugin still exists and create another network. The network creation fails.
{{ RESTART DAEMON }}
$ sudo docker plugin ls
ID NAME TAG DESCRIPTION ENABLED
fedd8eb3d5fb tiborvass/test-docker-netplugin latest Test network plugin for Docker true
$ sudo docker network create -d tiborvass/test-docker-netplugin:latest testnet3
Error response from daemon: could not resolve driver tiborvass/test-docker-netplugin:latest in registry
Describe the results you received:
The network creation fails with an enabled network plugin after a daemon restart