mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-14 04:39:33 +00:00
4eff0c8cf2
Add the notion of an "exit policy" to a pod. This policy controls the
behaviour when the last container of pod exits. Initially, there are
two policies:
- "continue" : the pod continues running. This is the default policy
when creating a pod.
- "stop" : stop the pod when the last container exits. This is the
default behaviour for `play kube`.
In order to implement the deferred stop of a pod, add a worker queue to
the libpod runtime. The queue will pick up work items and in this case
helps resolve dead locks that would otherwise occur if we attempted to
stop a pod during container cleanup.
Note that the default restart policy of `play kube` is "Always". Hence,
in order to really solve #13464, the YAML files must set a custom
restart policy; the tests use "OnFailure".
Fixes: #13464
Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
|
||
|---|---|---|
| .. | ||
| annotations.go | ||
| checkpoint_restore.go | ||
| config.go | ||
| container.go | ||
| container_inspect.go | ||
| containerstate.go | ||
| diff.go | ||
| errors.go | ||
| exec_codes.go | ||
| fileinfo.go | ||
| healthchecks.go | ||
| info.go | ||
| mount.go | ||
| pod_inspect.go | ||
| podstate.go | ||
| runtime.go | ||
| terminal.go | ||
| version.go | ||
| volume_inspect.go | ||