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
..
compat	Allow recursive dependency start with Init()	2020-06-18 09:34:04 -04:00
libpod	Allow recursive dependency start with Init()	2020-06-18 09:34:04 -04:00
swagger	add {generate,play} kube	2020-05-06 17:08:22 +02:00
utils	Merge pull request #6557 from rhatdan/lint	2020-06-15 09:19:40 -04:00
decoder.go	Fix Id->ID where possible for lint	2020-06-10 05:49:41 -04:00
types.go	Add some additional fields to imageinspect	2020-06-13 08:54:20 -04:00