5e97d2a1e2
Remove the non-OCI version of the configuration structure, and the parent image ID, from the ImageData that libkpod returns. At runtime, cri-o is only ever going to use the OCI configuration (possibly converted from another format by the image library) when setting up a container, so it can be confusing to display settings in "kpod inspect" that might be discarded when we try to run a container. Remove the non-OCI version of the configuration structure, and the hard-coded Type field, from the ContainerData that libkpod returns. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com> |
||
|---|---|---|
| .. | ||
| common | ||
| driver | ||
| image | ||
| sandbox | ||
| config.go | ||
| container.go | ||
| containerData.go | ||
| containerserver.go | ||