github.com/gunjan5/docker@v1.8.2/experimental/plugins_network.md (about) 1 # Experimental: Docker network driver plugins 2 3 Docker supports network driver plugins via 4 [LibNetwork](https://github.com/docker/libnetwork). Network driver plugins are 5 implemented as "remote drivers" for LibNetwork, which shares plugin 6 infrastructure with Docker. In effect this means that network driver plugins 7 are activated in the same way as other plugins, and use the same kind of 8 protocol. 9 10 ## Using network driver plugins 11 12 The means of installing and running a network driver plugin will depend on the 13 particular plugin. 14 15 Once running however, network driver plugins are used just like the built-in 16 network drivers: by being mentioned as a driver in network-oriented Docker 17 commands. For example, 18 19 docker network create -d weave mynet 20 21 Some network driver plugins are listed in [plugins.md](/docs/extend/plugins.md) 22 23 The network thus created is owned by the plugin, so subsequent commands 24 referring to that network will also be run through the plugin. 25 26 ## Network driver plugin protocol 27 28 The network driver protocol, additional to the plugin activation call, is 29 documented as part of LibNetwork: 30 [https://github.com/docker/libnetwork/blob/master/docs/remote.md](https://github.com/docker/libnetwork/blob/master/docs/remote.md). 31 32 # Related GitHub PRs and issues 33 34 Please record your feedback in the following issue, on the usual 35 Google Groups, or the IRC channel #docker-network. 36 37 - [#14083](https://github.com/docker/docker/issues/14083) Feedback on 38 experimental networking features 39 40 Other pertinent issues: 41 42 - [#13977](https://github.com/docker/docker/issues/13977) UI for using networks 43 - [#14023](https://github.com/docker/docker/pull/14023) --default-network option 44 - [#14051](https://github.com/docker/docker/pull/14051) --publish-service option 45 - [#13441](https://github.com/docker/docker/pull/13441) (Deprecated) Networks API & UI