summaryrefslogtreecommitdiff
path: root/cmd
diff options
context:
space:
mode:
authorbaude <bbaude@redhat.com>2019-02-26 10:19:08 -0600
committerbaude <bbaude@redhat.com>2019-02-26 10:19:08 -0600
commitc79c641da1df48b54de4d485c5d0fd9d2bf2849a (patch)
tree7867230a4ed20f05a7f5229ceae5645b796d2541 /cmd
parent507ab29cfedbcc7503fe10c44ea9e331c5a3a5ca (diff)
downloadpodman-c79c641da1df48b54de4d485c5d0fd9d2bf2849a.tar.gz
podman-c79c641da1df48b54de4d485c5d0fd9d2bf2849a.tar.bz2
podman-c79c641da1df48b54de4d485c5d0fd9d2bf2849a.zip
start pod containers recursively
when using the play kube command, we need to make sure that containers with dependancies are started in proper order. in this case, the infra container must be started first. Signed-off-by: baude <bbaude@redhat.com>
Diffstat (limited to 'cmd')
-rw-r--r--cmd/podman/play_kube.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/cmd/podman/play_kube.go b/cmd/podman/play_kube.go
index a59460b71..1a45cbed9 100644
--- a/cmd/podman/play_kube.go
+++ b/cmd/podman/play_kube.go
@@ -153,7 +153,7 @@ func playKubeYAMLCmd(c *cliconfig.KubePlayValues) error {
// start the containers
for _, ctr := range containers {
- if err := ctr.Start(ctx, false); err != nil {
+ if err := ctr.Start(ctx, true); err != nil {
// Making this a hard failure here to avoid a mess
// the other containers are in created status
return err