Files
podman/docs
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-05-11 16:05:10 +00:00
2018-01-18 07:01:48 -05:00
2017-11-01 11:24:59 -04:00
2019-02-14 15:03:11 -05:00
2019-02-14 15:03:11 -05:00
2018-08-30 16:51:56 +00:00
2018-12-19 14:20:55 -06:00
2018-12-04 08:03:49 -06:00
2018-08-30 16:51:56 +00:00
2018-12-19 14:20:55 -06:00
2018-12-19 14:20:55 -06:00
2018-12-03 12:00:18 -06:00
2018-08-30 16:51:56 +00:00
2018-08-30 16:51:56 +00:00
2018-08-30 16:51:56 +00:00
2018-08-30 16:51:56 +00:00
2018-08-30 16:51:56 +00:00
2018-08-30 16:51:56 +00:00
2018-12-07 10:27:41 -06:00
2018-08-30 16:51:56 +00:00
2018-08-30 16:51:56 +00:00
2018-08-30 16:51:56 +00:00
2018-12-06 09:10:45 -05:00
2018-09-30 07:48:41 +02:00
2018-12-06 10:17:16 +00:00
2019-02-14 13:21:52 -05:00