podman-init(1)

πŸ“¦
version 6.1.4 Β· 3 versions
, in arch rolling, fedora 43, fedora 44, ubuntu resolute

πŸ’– 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