podman/pkg/api
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
..
handlers Allow recursive dependency start with Init() 2020-06-18 09:34:04 -04:00
server fix misc remote build issues 2020-06-17 09:01:43 -05:00
types podman rmi: refactor logic 2020-04-21 08:12:25 +02:00
Makefile Rewire ListContainers for APIv2 libpod 2020-02-11 08:14:28 -06:00
tags.yaml network compatibility endpoints for API 2020-05-22 13:48:52 -05:00