spiegel_podman/pkg/api/handlers/libpod
Matthew Heon b20619e5b0 Allow recursive dependency start with Init()
As part of APIv2 Attach, we need to be able to attach to freshly
created containers (in ContainerStateConfigured). This isn't
something Libpod is interested in supporting, so we use Init() to
get the container into ContainerStateCreated, in which attach is
possible. Problem: Init() will fail if dependencies are not
started, so a fresh container in a fresh pod will fail. The
simplest solution is to extend the existing recursive start code
from Start() to Init(), allowing dependency containers to be
started when we initialize the container (optionally, controlled
via bool).

Also, update some comments in container_api.go to make it more
clear how some of our major API calls work.

Fixes #6646

Signed-off-by: Matthew Heon <mheon@redhat.com>
2020-06-18 09:34:04 -04:00
..
containers.go Allow recursive dependency start with Init() 2020-06-18 09:34:04 -04:00
containers_create.go Re-add resource limit warnings to Specgen 2020-06-16 17:32:01 -04:00
copy.go v2 copy endpoints 2020-05-26 12:04:20 -05:00
generate.go add {generate,play} kube 2020-05-06 17:08:22 +02:00
healthcheck.go Fix remote integration for healthchecks 2020-05-20 14:43:01 -05:00
images.go Fix leak of empty tarball 2020-06-01 10:07:58 -05:00
info.go refactor info 2020-04-06 12:45:42 -05:00
manifests.go compat handlers: add X-Registry-Auth header support 2020-05-29 15:39:37 +02:00
networks.go enable podman v2 networking for remote client 2020-05-12 13:23:43 -05:00
play.go compat handlers: add X-Registry-Auth header support 2020-05-29 15:39:37 +02:00
pods.go Turn on More linters 2020-06-15 07:05:56 -04:00
swagger.go enable podman v2 networking for remote client 2020-05-12 13:23:43 -05:00
system.go Turn on More linters 2020-06-15 07:05:56 -04:00
volumes.go Turn on More linters 2020-06-15 07:05:56 -04:00