From 5920bfa2efd07f6020a384609730928c26e913d5 Mon Sep 17 00:00:00 2001 From: Matt Heon Date: Tue, 12 Sep 2023 13:28:42 -0400 Subject: [PATCH] The `podman init` command cannot modify containers. `podman init` is a debugging command for inspecting a container's OCI spec before it runs, to look for anything suspicious. It is not capable of supporting modifications to that spec, as it starts Conmon and thus the OCI runtime, so the spec has already been loaded by the time `podman init` is run. Signed-off-by: Matt Heon --- docs/source/markdown/podman-init.1.md.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/markdown/podman-init.1.md.in b/docs/source/markdown/podman-init.1.md.in index 9f5e516f1d..e883d53a5d 100644 --- a/docs/source/markdown/podman-init.1.md.in +++ b/docs/source/markdown/podman-init.1.md.in @@ -13,7 +13,7 @@ Initialize one or more containers. You may use container IDs or names as input. Initializing a container performs all tasks necessary for starting the container (mounting filesystems, creating an OCI spec, initializing the container network) but does not start the container. If a container is not initialized, the `podman start` and `podman run` commands initialize it automatically prior to starting it. -This command is intended to be used for inspecting or modifying the container's filesystem or OCI spec prior to starting it. +This command is intended to be used for inspecting a container's filesystem or OCI spec prior to starting it. This can be used to inspect the container before it runs, or debug why a container is failing to run. ## OPTIONS