kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity

Update File mount info for docker v1.1.0

Browse source 
Docker-DCO-1.1-Signed-off-by: Tom Fotherby <github@tomfotherby.com> (github: tomfotherby)
This commit is contained in:
Tom Fotherby 2014-07-05 03:46:41 +01:00
parent cfbe062eb2
commit 87df57810d
1 changed files with 4 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docs/sources/userguide/dockervolumes.md
View file

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