new repository

1 files changed, 10 insertions, 0 deletions

diff --git a/devdocs/docker/engine%2Fextend%2Fplugins_network%2Findex.html b/devdocs/docker/engine%2Fextend%2Fplugins_network%2Findex.html
new file mode 100644
index 00000000..904b68cc
--- /dev/null
+++ b/devdocs/docker/engine%2Fextend%2Fplugins_network%2Findex.html
@@ -0,0 +1,10 @@
+ <h1 id="docker-network-driver-plugins">Docker network driver plugins</h1> <p>This document describes Docker Engine network driver plugins generally available in Docker Engine. To view information on plugins managed by Docker Engine, refer to <a href="../index">Docker Engine plugin system</a>.</p> <p>Docker Engine network plugins enable Engine deployments to be extended to support a wide range of networking technologies, such as VXLAN, IPVLAN, MACVLAN or something completely different. Network driver plugins are supported via the LibNetwork project. Each plugin is implemented as a “remote driver” for LibNetwork, which shares plugin infrastructure with Engine. Effectively, network driver plugins are activated in the same way as other plugins, and use the same kind of protocol.</p> <h2 id="network-plugins-and-swarm-mode">Network plugins and swarm mode</h2> <p><a href="../legacy_plugins/index">Legacy plugins</a> do not work in swarm mode. However, plugins written using the <a href="../index">v2 plugin system</a> do work in swarm mode, as long as they are installed on each swarm worker node.</p> <h2 id="use-network-driver-plugins">Use network driver plugins</h2> <p>The means of installing and running a network driver plugin depend on the particular plugin. So, be sure to install your plugin according to the instructions obtained from the plugin developer.</p> <p>Once running however, network driver plugins are used just like the built-in network drivers: by being mentioned as a driver in network-oriented Docker commands. For example,</p> <div class="highlight"><pre class="highlight" data-language="">$ docker network create --driver weave mynet
+</pre></div> <p>Some network driver plugins are listed in <a href="../legacy_plugins/index">plugins</a></p> <p>The <code class="language-plaintext highlighter-rouge">mynet</code> network is now owned by <code class="language-plaintext highlighter-rouge">weave</code>, so subsequent commands referring to that network will be sent to the plugin,</p> <div class="highlight"><pre class="highlight" data-language="">$ docker run --network=mynet busybox top
+</pre></div> <h2 id="find-network-plugins">Find network plugins</h2> <p>Network plugins are written by third parties, and are published by those third parties, either on <a href="https://store.docker.com/search?category=network&amp;q=&amp;type=plugin">Docker Store</a> or on the third party’s site.</p> <h2 id="write-a-network-plugin">Write a network plugin</h2> <p>Network plugins implement the <a href="../plugin_api/index">Docker plugin API</a> and the network plugin protocol</p> <h2 id="network-plugin-protocol">Network plugin protocol</h2> <p>The network driver protocol, in addition to the plugin activation call, is documented as part of libnetwork: <a href="https://github.com/docker/libnetwork/blob/master/docs/remote/">https://github.com/docker/libnetwork/blob/master/docs/remote.md</a>.</p> <h2 id="related-information">Related Information</h2> <p>To interact with the Docker maintainers and other interested users, see the IRC channel <code class="language-plaintext highlighter-rouge">#docker-network</code>.</p> <ul> <li><a href="https://docs.docker.com/network/">Docker networks feature overview</a></li> <li>The <a href="https://github.com/docker/libnetwork">LibNetwork</a> project</li> </ul> 
+<p><a href="https://docs.docker.com/search/?q=Examples">Examples</a>, <a href="https://docs.docker.com/search/?q=Usage">Usage</a>, <a href="https://docs.docker.com/search/?q=plugins">plugins</a>, <a href="https://docs.docker.com/search/?q=docker">docker</a>, <a href="https://docs.docker.com/search/?q=documentation">documentation</a>, <a href="https://docs.docker.com/search/?q=user%20guide">user guide</a></p>
+<div class="_attribution">
+  <p class="_attribution-p">
+    &copy; 2019 Docker, Inc.<br>Licensed under the Apache License, Version 2.0.<br>Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries.<br>Docker, Inc. and other parties may also have trademark rights in other terms used herein.<br>
+    <a href="https://docs.docker.com/engine/extend/plugins_network/" class="_attribution-link">https://docs.docker.com/engine/extend/plugins_network/</a>
+  </p>
+</div>