Fix minor typos, add a clarification
Clarification about volumes removal.
This commit is contained in:
parent
d84796ce3f
commit
9cff9cec42
|
|
@ -86,11 +86,13 @@ If you remove every container and volume all your data will be lost, and the nex
|
|||
|
||||
For persistence of the Magento deployment, the above examples define docker volumes namely `mariadb_data`, `magento_data`, `apache_data` and `php_data`. The Magento application state will persist as long as these volumes are not removed.
|
||||
|
||||
To avoid inadvertent removal of these volumes you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data.
|
||||
|
||||
> **Note!** If you have already started using your application, follow the steps on [backing](#backing-up-your-application) up to pull the data from your running container down to your host.
|
||||
|
||||
### Mount host directories as data volumes with Docker Compose
|
||||
|
||||
This requires a sightly modification from the `docker-compose.yml` template previously shown:
|
||||
TThis requires a minor change to the `docker-compose.yml` template previously shown:
|
||||
```
|
||||
version: '2'
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue