toolshed/docker-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #28602 from dattatrayakumbhar04/nw-connect-paused-container-doc

Browse Source 
28600: Docs: network connect for container in Created/Stopped state
Upstream-commit: b3687bdcdc9e52a1cc154648262c69939d8633df
Component: engine
This commit is contained in:
Sebastiaan van Stijn
2016-11-24 15:04:53 +01:00
committed by GitHub
parent 8d1d4dee5b 57d2ffce2e
commit 92d40c923d
2 changed files with 2 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
components/engine/docs/reference/commandline/network_connect.md
+1 -4
View File
@@ -61,11 +61,8 @@ being connected to.
```bash
$ docker network connect --alias db --alias mysql multi-host-network container2
```
You can pause, restart, and stop containers that are connected to a network.
Paused containers remain connected and can be revealed by a `network inspect`.
When the container is stopped, it does not appear on the network until you restart
it.
A container connects to its configured networks when it runs.
If specified, the container's IP address(es) is reapplied when a stopped
container is restarted. If the IP address is no longer available, the container
components/engine/man/docker-network-connect.1.md
+1 -4
View File
@@ -24,11 +24,8 @@ You can also use the `docker run --net=<network-name>` option to start a contain
```bash
$ docker run -itd --net=multi-host-network --ip 172.20.88.22 --ip6 2001:db8::8822 busybox
```
You can pause, restart, and stop containers that are connected to a network.
Paused containers remain connected and can be revealed by a `network inspect`.
When the container is stopped, it does not appear on the network until you restart
it.
A container connects to its configured networks when it runs.
If specified, the container's IP address(es) is reapplied when a stopped
container is restarted. If the IP address is no longer available, the container