Andreas/docker-cheat-sheet
1
0
Fork 0
mirror of https://github.com/wsargent/docker-cheat-sheet.git synced 2025-12-16 15:10:12 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #136 from phoen1x/patch-1

Browse source 
Volumes can be files
This commit is contained in:
Will Sargent 2017-07-19 11:34:20 -07:00 • committed by GitHub
commit f7a679fd34
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
README.md
View file

@ -419,6 +419,8 @@ You can use remote NFS volumes if you're [feeling brave](https://docs.docker.com
You may also consider running data-only containers as described [here](http://container42.com/2013/12/16/persistent-volumes-with-docker-container-as-volume-pattern/) to provide some data portability.
[Be aware that you can mount files as volumes.](#volumes-can-be-files)
## Exposing ports
Exposing incoming ports through the host container is [fiddly but doable](https://docs.docker.com/engine/reference/run/#expose-incoming-ports).
@ -760,6 +762,21 @@ Remove all exited containers
docker rm -f $(docker ps -a | grep Exit | awk '{ print $1 }')
```
### Volumes can be files
Be aware that you can mount files as volumes. For example you can inject a configuration file like this:
``` bash
# copy file from container
docker run --rm httpd cat /usr/local/apache2/conf/httpd.conf > httpd.conf
# edit file
vim httpd.conf
# start container with modified configuration
docker run --rm -ti -v "$PWD/httpd.conf:/usr/local/apache2/conf/httpd.conf:ro" -p "80:80" httpd
```
## Contributing
Here's how to contribute to this cheat sheet.