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