Docker-DCO-1.1-Signed-off-by: Tom Fotherby <github@tomfotherby.com> (github: tomfotherby)
| ... | ... |
@@ -78,13 +78,12 @@ As well as directories, the `-v` flag can be used to mount a single file from th |
| 78 | 78 |
$ sudo docker run --rm -it -v ~/.bash_history:/.bash_history ubuntu /bin/bash |
| 79 | 79 |
|
| 80 | 80 |
This will drop you into a bash shell in a new container, you will have your bash history from your host and when |
| 81 |
-you exit the container the host will have the history of the commands typed while in the container. |
|
| 81 |
+you exit the container, the host will have the history of the commands typed while in the container. |
|
| 82 | 82 |
|
| 83 | 83 |
> **Note:** |
| 84 |
-> The two-way binding of the mounted file will only be preserved as long as the inode doesn't change. Many |
|
| 85 |
-> tools used to edit files including `vi` and `sed --in-place` may result in a inode change. In the case where you |
|
| 86 |
-> want to edit the file, it is often best to mount the parent directory. |
|
| 87 |
- |
|
| 84 |
+> Many tools used to edit files including `vi` and `sed --in-place` may result in a inode change. Since docker v1.1.0 |
|
| 85 |
+> this will produce a error such as "*sed: cannot rename ./sedKdJ9Dy: Device or resource busy*". In the case where you |
|
| 86 |
+> want to edit the mounted file, it is often easiest to instead mount the parent directory. |
|
| 88 | 87 |
|
| 89 | 88 |
## Creating and mounting a Data Volume Container |
| 90 | 89 |
|