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

add small doc

Browse Source 
Signed-off-by: Victor Vieux <vieux@docker.com>
Upstream-commit: 26feb09fac7cfcafef36cc71df1176301c70eb53
Component: engine
This commit is contained in:
Victor Vieux
2014-08-14 00:26:44 +00:00
parent fb74f9294f
commit 09240bd768
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
components/engine/docs/sources/articles/networking.md
View File

@ -731,3 +731,14 @@ usual containers. But unless you have very specific networking needs
that drive you to such a solution, it is probably far preferable to use
`--icc=false` to lock down inter-container communication, as we explored
earlier.
## Editing networking config files
Starting with Docker v.1.2.0, you can now edit `/etc/hosts`, `/etc/hostname`
and `/etc/resolve.conf` in a running container. This is useful if you need
to install bind or other services that might override one of those files.
Note, however, that changes to these files will not be saved by
`docker commit`, nor will they be saved during `docker run`.
That means they won't be saved in the image, nor will they persist when a
container is restarted; they will only "stick" in a running container.