Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs/extend: fix broken link and some markdown touch-ups 

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Sebastiaan van Stijn 2020-05-28 17:28:43 +02:00
parent 590f3271ef
commit a968359e08
No known key found for this signature in database
GPG Key ID: 76698F39D527CE8C
2 changed files with 62 additions and 58 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/extend/plugins_network.md
View File

@ -42,14 +42,18 @@ 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 network drivers: by being mentioned as a driver in network-oriented Docker
commands. For example, commands. For example,
```bash
$ docker network create --driver weave mynet $ docker network create --driver weave mynet
```
Some network driver plugins are listed in [plugins](legacy_plugins.md) Some network driver plugins are listed in [plugins](legacy_plugins.md)
The `mynet` network is now owned by `weave`, so subsequent commands The `mynet` network is now owned by `weave`, so subsequent commands
referring to that network will be sent to the plugin, referring to that network will be sent to the plugin,
```bash
$ docker run --network=mynet busybox top $ docker run --network=mynet busybox top
```
## Find network plugins ## Find network plugins
@ -61,8 +65,8 @@ or on the third party's site.
## Write a network plugin ## Write a network plugin
Network plugins implement the [Docker plugin Network plugins implement the [Docker plugin API](plugin_api.md) and the network
API](plugin_api.md) and the network plugin protocol plugin protocol
## Network plugin protocol ## Network plugin protocol