podman/test/trust_set_test.json

{
    "default": [
        {
            "type": "insecureAcceptAnything"
        }
    ],
    "transports": null
}
pod infra container is started before a container in a pod is run, started, or attached. 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> 2019-02-15 21:39:24 +00:00			`{`
			`"default": [`
			`{`
			`"type": "insecureAcceptAnything"`
			`}`
			`],`
			`"transports": null`
			`}`