podman-init(1)
π podman-init(1) β bestie edition π
okay so this is podman-init, from the General Commands Manual section of your local man pages, and it's about to become your new fave. no cap.
β¨ NAME β¨
podman-init β Initialize one or more containers π
πΈ SYNOPSIS πΈ
podman init [options] container [container...]
podman container init [options] container [container...]
two ways in, same vibe. pick whichever one sparks joy π
π¦ DESCRIPTION π¦
So like. You can initialize one or more containers, and you can hand over container IDs or names as input β either one works, she's flexible like that. πβοΈ
Initializing a container does all the tasks necessary for starting the container:
- mounting filesystems
- creating an OCI spec
- initializing the container network
β¦but it does NOT actually start the container. that's the whole point bestie, it's the getting-ready-not-going-yet moment. π§
and here's the thing: if a container isn't initialized, podman start and podman run will initialize it automatically prior to starting it. so like, they got you. but this command exists for a reason β
This command is intended to be used for inspecting a container's filesystem or OCI spec prior to starting it. so you can peek inside the container before it runs, or debug why a container is failing to run. literally the "look before you leap" of containers. π
π OPTIONS π
--all,-aβ Initialize all containers. Containers that have already initialized (including containers that have been started and are running) are ignored. she's not gonna double-dip, she knows who's already done. β¨--latest,-lβ Instead of providing the container name or ID, use the last created container. π
β οΈ Note: the last started container can be from other users of Podman on the host machine. so like, heads up.
Also, this option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines. π«Ά
π EXAMPLES π
Initialize specified container with a given ID. π
$ podman init 35480fc9d568
Initialize specified container with a given name. π·οΈ
$ podman init test1
Initialize the latest container. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines) π
$ podman init --latest
Initialize all containers. π (look at all these hashes go)
$ podman init --all
9d2629dda7b9d4ca35c1fc63fa56592a08b9d5ab988b4301fddf16b623f676cc
a9b78bcac97e131236930e3fa0be576e95ab89c96a7cb6fb1c821b772db9f623
9db345273719c14bc254f90ef2df24779193b42d68b1364c0914ca6f76cf5e9c
π SEE ALSO π
podman(1), podman-start(1) β go read those too, they're lowkey iconic π«Ά
π HISTORY π
April 2019, Originally compiled by Matthew Heon mheon@redhat.com β¨mailto:mheon@redhat.comβ© β thank you king, we stan. π
and that's the whole page, bestie!! π the footer says podman-init(1), it's from the General Commands Manual crew, and it's giving very April 2019 energy. go init something. not start it. just init it. πβ¨π¦πΈπ
π₯ππβπ
π¦ where this page comes from
- arch rolling: podman-docker 6.1.4-1 Β· Apache-2.0
- fedora 43: podman-docker 5:5.6.2-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 43: podman-docker 5:5.8.4-1.fc43
- fedora 43: podman-docker 5:5.8.8-1.fc43
- fedora 43: podman-docker 5:5.8.9-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.1-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.7-1.fc44
- fedora 44: podman-docker 5:5.8.9-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- ubuntu resolute: podman-docker 5.7.0+ds2-3build1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms