4ac92d73e4
The way we build the OCI Process Args slice is incorrect. With the current implementation we may for example end up building this slice with only the entry point arguments, if the kubelet passed information is missing the Command slice. We also will end up building the Args slice with the Image config process arguments, without the defined entry point, if kubelet does not tell us anything about the container process command to be run. This patch fixes that by favoring the kubelet ContainerConfig information. If that is missing, we try to complete it with the container image information. We always use ContainerConfig.Command[] or ImageConfig.EntryPoint[] as the first OCI Process Args slice entries. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> |
||
---|---|---|
.. | ||
apparmor | ||
seccomp | ||
config.go | ||
container.go | ||
container_attach.go | ||
container_create.go | ||
container_exec.go | ||
container_execsync.go | ||
container_list.go | ||
container_portforward.go | ||
container_remove.go | ||
container_start.go | ||
container_status.go | ||
container_stop.go | ||
container_updateruntimeconfig.go | ||
image_list.go | ||
image_pull.go | ||
image_remove.go | ||
image_status.go | ||
runtime_status.go | ||
sandbox.go | ||
sandbox_list.go | ||
sandbox_remove.go | ||
sandbox_run.go | ||
sandbox_status.go | ||
sandbox_stop.go | ||
server.go | ||
utils.go | ||
version.go |