Skip to content

Commit d2dacb2

Browse files
author
Matthew Fisher
committed
docs(components): explain a container's filesystem
This explains that a container's filesystem is ephemeral, and that any changes made to disk will be wiped when the container is either stopped or restarted.
1 parent 48aa7d7 commit d2dacb2

1 file changed

Lines changed: 11 additions & 2 deletions

File tree

docs/components/container.rst

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,16 @@
77
Container
88
=========
99
Deis containers are instances of `Docker`_ containers used to run :ref:`Applications <application>`.
10-
Containers perform the actual work of an :ref:`application` by servicing requests or running
10+
Containers perform the actual work of an :ref:`application` by servicing requests or running
1111
background tasks as part of the :ref:`Formation's <formation>` runtime :ref:`Layer`.
1212

13-
.. _`Docker`: http://docker.io/
13+
Ephemeral Filesystem
14+
--------------------
15+
16+
Each container gets its own ephemeral filesystem, with a fresh copy of the most recently
17+
deployed code. During the container’s lifetime, its running processes can use the
18+
filesystem as a temporary scratchpad, but no files that are written are visible to
19+
processes in any other container. Any files written to the ephemeral filesystem will be
20+
discarded the moment the container is either stopped or restarted.
21+
22+
.. _`Docker`: http://docker.io/

0 commit comments

Comments
 (0)