github.com/a4a881d4/docker@v1.9.0-rc2/docs/extend/plugins_network.md (about) 1 <!--[metadata]> 2 +++ 3 title = "Docker network driver plugins" 4 description = "Network drive plugins." 5 keywords = ["Examples, Usage, plugins, docker, documentation, user guide"] 6 [menu.main] 7 parent = "mn_extend" 8 weight=-1 9 +++ 10 <![end-metadata]--> 11 12 # Docker network driver plugins 13 14 Docker supports network driver plugins via 15 [LibNetwork](https://github.com/docker/libnetwork). Network driver plugins are 16 implemented as "remote drivers" for LibNetwork, which shares plugin 17 infrastructure with Docker. In effect this means that network driver plugins 18 are activated in the same way as other plugins, and use the same kind of 19 protocol. 20 21 ## Using network driver plugins 22 23 The means of installing and running a network driver plugin will depend on the 24 particular plugin. 25 26 Once running however, network driver plugins are used just like the built-in 27 network drivers: by being mentioned as a driver in network-oriented Docker 28 commands. For example, 29 30 docker network create -d weave mynet 31 32 Some network driver plugins are listed in [plugins](plugins.md) 33 34 The network thus created is owned by the plugin, so subsequent commands 35 referring to that network will also be run through the plugin such as, 36 37 docker run --net=mynet busybox top 38 39 ## Network driver plugin protocol 40 41 The network driver protocol, additional to the plugin activation call, is 42 documented as part of LibNetwork: 43 [https://github.com/docker/libnetwork/blob/master/docs/remote.md](https://github.com/docker/libnetwork/blob/master/docs/remote.md). 44 45 # Related GitHub PRs and issues 46 47 Please record your feedback in the following issue, on the usual 48 Google Groups, or the IRC channel #docker-network. 49 50 - [#14083](https://github.com/docker/docker/issues/14083) Feedback on 51 experimental networking features