podman-system-renumber(1)
π podman-system-renumber(1) β General Commands Manual π
okay bestie, sit down, we're doing the lock renumbering episode of the podman cinematic universe and honestly? it's giving maintenance-core, but it's important. this is the podman-system-renumber manual page, and no cap, you're gonna want to read it before you start messing with num_locks. β¨
πΈ NAME πΈ
podman-system-renumber β migrate lock numbers to handle a change in maximum number of locks π¦
π«Ά SYNOPSIS π«Ά
podman system renumber
β¨ DESCRIPTION β¨
so, podman system renumber renumbers the locks that containers and pods use. that's it, that's the whole job, but omg the why is the juicy part.
every single Podman container and every single pod gets allocated a lock at creation time, and there's a maximum number of those locks, controlled by the num_locks parameter in containers.conf. π
when all the available locks are exhausted, that's it β no further containers and pods can be created until some existing containers and pods are removed. π the way around this is to bump up the number of locks available by modifying containers.conf, and then running podman system renumber to prepare the new locks (and reallocate lock numbers to fit the new struct). iconic.
β οΈpodman system renumbermust be called after any changes tonum_locks. failure to do so results in errors starting Podman, because the number of locks available conflicts with the configured number of locks. not a vibe, fr fr.
podman system renumber can also be used to migrate 1.0 and earlier versions of Podman β which used a totally different locking scheme β to the new locking model. it is not strictly required to do this, but it is highly recommended to do so, because deadlocks can occur otherwise. π
and one last thing, if possible, avoid calling podman system renumber while there are other Podman processes running. please. for me. π
π EXAMPLES π
renumber container and pod locks after modifying the num_locks setting in containers.conf:
$ podman system renumber
π SEE ALSO π
π HISTORY π
February 2019, originally compiled by Matt Heon (mheon at redhat dot com) π
and that's the page, bestie!! this was podman-system-renumber(1), from the General Commands Manual, dated February 2019 β go forth, renumber those locks, and slay. π
β¨π
π¦ 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