mirror of
https://github.com/containers/podman
synced 2024-10-19 16:54:07 +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>
21 lines
331 B
Plaintext
21 lines
331 B
Plaintext
/.artifacts/
|
|
/_output/
|
|
/conmon/conmon.o
|
|
/docs/*.[158]
|
|
/docs/*.[158].gz
|
|
*.o
|
|
*.orig
|
|
/pause/pause.o
|
|
/bin/
|
|
/test/bin2img/bin2img
|
|
/test/checkseccomp/checkseccomp
|
|
/test/copyimg/copyimg
|
|
/build/
|
|
.nfs*
|
|
.ropeproject
|
|
__pycache__
|
|
/cmd/podman/varlink/ioprojectatomicpodman.go
|
|
/cmd/podman/varlink/iopodman.go
|
|
.gopathok
|
|
test/e2e/e2e.coverprofile
|