Files
podman/test/e2e
Peter Hunt 81804fc464 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>
2019-02-15 16:39:24 -05:00
..
2018-04-05 14:13:49 +00:00
2019-02-05 10:05:41 -06:00
2019-01-18 15:43:11 -06:00
2019-02-09 20:00:19 -05:00
2019-02-08 10:26:43 -06:00
2019-01-15 08:19:26 -06:00
2019-01-21 15:23:30 -06:00