stated 2 problems in a better for volumes
This commit is contained in:
parent
13ea6b9087
commit
e517e3ab99
|
|
@ -12,10 +12,13 @@ weight: 10
|
|||
<!-- overview -->
|
||||
|
||||
On-disk files in a container are ephemeral, which presents some problems for
|
||||
non-trivial applications when running in containers. One problem
|
||||
is the loss of files when a container crashes. The kubelet restarts the container
|
||||
but with a clean state. A second problem occurs when sharing files
|
||||
between containers running together in a `Pod`.
|
||||
non-trivial applications when running in containers. One problem occurs when
|
||||
a container crashes or is stopped. Container state is not saved so all of the
|
||||
files that were created or modified during the lifetime of the container are lost.
|
||||
During a crash, kubelet restarts the container with a clean state.
|
||||
Another problem occurs when multiple containers are running in a `Pod` and
|
||||
need to share files. It can be challenging to setup
|
||||
and access a shared filesystem across all of the containers.
|
||||
The Kubernetes {{< glossary_tooltip text="volume" term_id="volume" >}} abstraction
|
||||
solves both of these problems.
|
||||
Familiarity with [Pods](/docs/concepts/workloads/pods/) is suggested.
|
||||
|
|
|
|||
Loading…
Reference in New Issue