mirror of
https://github.com/containers/podman
synced 2024-10-20 09:13:46 +00:00
81804fc464
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>
12 lines
767 B
Plaintext
12 lines
767 B
Plaintext
mode: atomic
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:14.46,21.20 2 1
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:31.2,31.19 1 1
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:38.2,38.53 1 1
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:65.2,65.52 1 1
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:21.20,23.17 2 2
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:26.3,28.36 3 2
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:23.17,25.4 1 0
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:31.19,36.3 4 2
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:38.53,63.3 20 1
|
|
github.com/containers/libpod/test/e2e/pod_pod_namespaces.go:65.52,90.3 20 1
|