summaryrefslogtreecommitdiff
path: root/libpod/container.go
diff options
context:
space:
mode:
authorValentin Rothberg <rothberg@redhat.com>2019-12-12 12:11:12 +0100
committerValentin Rothberg <rothberg@redhat.com>2019-12-13 14:39:45 +0100
commit437bc61f4e64d132736066330b18f327bffe48fa (patch)
treeafea7e5c5200246a4c3ad1c86fd16a12ba339ee7 /libpod/container.go
parentf81f15f42250a642f0753b5f18be61c1f24931dd (diff)
downloadpodman-437bc61f4e64d132736066330b18f327bffe48fa.tar.gz
podman-437bc61f4e64d132736066330b18f327bffe48fa.tar.bz2
podman-437bc61f4e64d132736066330b18f327bffe48fa.zip
container config: add CreateCommand
Store the full command plus arguments of the process the container has been created with. Expose this data as a `Config.CreateCommand` field in the container-inspect data as well. This information can be useful for debugging, as we can find out which command has created the container, and, if being created via the Podman CLI, we know exactly with which flags the container has been created with. The immediate motivation for this change is to use this information for `podman-generate-systemd` to generate systemd-service files that allow for creating new containers (in contrast to only starting existing ones). Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'libpod/container.go')
-rw-r--r--libpod/container.go4
1 files changed, 4 insertions, 0 deletions
diff --git a/libpod/container.go b/libpod/container.go
index dcec3ee50..2693190b5 100644
--- a/libpod/container.go
+++ b/libpod/container.go
@@ -232,6 +232,10 @@ type ContainerConfig struct {
// ID of this container's lock
LockID uint32 `json:"lockID"`
+ // CreateCommand is the full command plus arguments of the process the
+ // container has been created with.
+ CreateCommand []string `json:"CreateCommand,omitempty"`
+
// TODO consider breaking these subsections up into smaller structs
// UID/GID mappings used by the storage