diff options
| author | Peter Hunt <pehunt@redhat.com> | 2019-02-15 16:39:24 -0500 |
|---|---|---|
| committer | Peter Hunt <pehunt@redhat.com> | 2019-02-15 16:39:24 -0500 |
| commit | 81804fc4641d279fec8f9bf48b21b22fc90cb891 (patch) | |
| tree | b997e2f6e703b722cc955d14b26937fcecf45828 /docs/podman-history.1.md | |
| parent | 0a521e139faa0c7f1d9b6c9e647c350c1b7c4e04 (diff) | |
| download | podman-81804fc4641d279fec8f9bf48b21b22fc90cb891.tar.gz podman-81804fc4641d279fec8f9bf48b21b22fc90cb891.tar.bz2 podman-81804fc4641d279fec8f9bf48b21b22fc90cb891.zip | |
pod infra container is started before a container in a pod is run, started, or attached.
Prior, a pod would have to be started immediately when created, leading to confusion about what a pod state should be immediately after creation. The problem was podman run --pod ... would error out if the infra container wasn't started (as it is a dependency). Fix this by allowing for recursive start, where each of the container's dependencies are started prior to the new container. This is only applied to the case where a new container is attached to a pod.
Also rework container_api Start, StartAndAttach, and Init functions, as there was some duplicated code, which made addressing the problem easier to fix.
Signed-off-by: Peter Hunt <pehunt@redhat.com>
Diffstat (limited to 'docs/podman-history.1.md')
0 files changed, 0 insertions, 0 deletions