diff options
author | Matthew Heon <matthew.heon@pm.me> | 2019-07-08 18:37:40 -0400 |
---|---|---|
committer | Matthew Heon <mheon@redhat.com> | 2019-07-17 16:48:38 -0400 |
commit | 1e3e99f2fe95c8679f8962b8175038bd7d0558f2 (patch) | |
tree | 6e89a46149e14fa1f539b61880bf76c30aa7d990 /libpod/image/pull.go | |
parent | 1c02905ec7af9f63a35ee05e9e9ce594c45c4c58 (diff) | |
download | podman-1e3e99f2fe95c8679f8962b8175038bd7d0558f2.tar.gz podman-1e3e99f2fe95c8679f8962b8175038bd7d0558f2.tar.bz2 podman-1e3e99f2fe95c8679f8962b8175038bd7d0558f2.zip |
Move the HostConfig portion of Inspect inside libpod
When we first began writing Podman, we ran into a major issue
when implementing Inspect. Libpod deliberately does not tie its
internal data structures to Docker, and stores most information
about containers encoded within the OCI spec. However, Podman
must present a CLI compatible with Docker, which means it must
expose all the information in 'docker inspect' - most of which is
not contained in the OCI spec or libpod's Config struct.
Our solution at the time was the create artifact. We JSON'd the
complete CreateConfig (a parsed form of the CLI arguments to
'podman run') and stored it with the container, restoring it when
we needed to run commands that required the extra info.
Over the past month, I've been looking more at Inspect, and
refactored large portions of it into Libpod - generating them
from what we know about the OCI config and libpod's (now much
expanded, versus previously) container configuration. This path
comes close to completing the process, moving the last part of
inspect into libpod and removing the need for the create
artifact.
This improves libpod's compatability with non-Podman containers.
We no longer require an arbitrarily-formatted JSON blob to be
present to run inspect.
Fixes: #3500
Signed-off-by: Matthew Heon <matthew.heon@pm.me>
Diffstat (limited to 'libpod/image/pull.go')
0 files changed, 0 insertions, 0 deletions