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

Merge pull request #4707 from thaJeztah/fix_overlay_typo 

docs: fix typo in "network create" docs
This commit is contained in:
Sebastiaan van Stijn 2023-12-11 22:48:02 +01:00 committed by GitHub
parent 4dd5c23d6e 0a94d85cd6
commit ce6832a355
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/reference/commandline/network_create.md
View File

@ -61,7 +61,7 @@ to access the network stack of a swarm service.
The `--attachable` option used in the example above disables this restriction, The `--attachable` option used in the example above disables this restriction,
and allows for both swarm services and manually started containers to attach to and allows for both swarm services and manually started containers to attach to
the oerlay network. the overlay network.
Network names must be unique. The Docker daemon attempts to identify naming Network names must be unique. The Docker daemon attempts to identify naming
conflicts but this is not guaranteed. It is the user's responsibility to avoid conflicts but this is not guaranteed. It is the user's responsibility to avoid

2
man/src/network/create.md
View File

@ -30,7 +30,7 @@ to access the network stack of a swarm service.
The `--attachable` option used in the example above disables this restriction, The `--attachable` option used in the example above disables this restriction,
and allows for both swarm services and manually started containers to attach to and allows for both swarm services and manually started containers to attach to
the oerlay network. the overlay network.
Network names must be unique. The Docker daemon attempts to identify naming Network names must be unique. The Docker daemon attempts to identify naming
conflicts but this is not guaranteed. It is the user's responsibility to avoid conflicts but this is not guaranteed. It is the user's responsibility to avoid