Data exists in stopped containers, but not removed containers

Signed-off-by: Brandon Mitchell <git@bmitch.net>
This commit is contained in:
Brandon Mitchell 2018-11-16 07:34:20 -05:00
parent 09e2efeaeb
commit 906a91f5ea
1 changed files with 1 additions and 1 deletions

View File

@ -9,7 +9,7 @@ redirect_from:
By default all files created inside a container are stored on a writable
container layer. This means that:
- The data doesn't persist when that container is no longer running, and it can be
- The data doesn't persist when that container no longer exists, and it can be
difficult to get the data out of the container if another process needs it.
- A container's writable layer is tightly coupled to the host machine
where the container is running. You can't easily move the data somewhere else.