diff options
| author | Daniel J Walsh <dwalsh@redhat.com> | 2020-07-20 14:17:37 -0400 |
|---|---|---|
| committer | Daniel J Walsh <dwalsh@redhat.com> | 2020-07-20 15:09:54 -0400 |
| commit | 841eac0af651d7afa4749a65f4e773815b5c715c (patch) | |
| tree | c77b9d49238626f93839206c37da8bf7d8b9505b /docs/source/markdown/podman-system-renumber.1.md | |
| parent | 0d26a573e3cf8cc5baea84206a86cb83b433b6d5 (diff) | |
| download | podman-841eac0af651d7afa4749a65f4e773815b5c715c.tar.gz podman-841eac0af651d7afa4749a65f4e773815b5c715c.tar.bz2 podman-841eac0af651d7afa4749a65f4e773815b5c715c.zip | |
Switch references from libpod.conf to containers.conf
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'docs/source/markdown/podman-system-renumber.1.md')
| -rw-r--r-- | docs/source/markdown/podman-system-renumber.1.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/source/markdown/podman-system-renumber.1.md b/docs/source/markdown/podman-system-renumber.1.md index 071eefe29..51c085606 100644 --- a/docs/source/markdown/podman-system-renumber.1.md +++ b/docs/source/markdown/podman-system-renumber.1.md @@ -9,9 +9,9 @@ podman\-system\-renumber - Migrate lock numbers to handle a change in maximum nu ## DESCRIPTION **podman system renumber** renumbers locks used by containers and pods. -Each Podman container and pod is allocated a lock at creation time, up to a maximum number controlled by the **num_locks** parameter in **libpod.conf**. +Each Podman container and pod is allocated a lock at creation time, up to a maximum number controlled by the **num_locks** parameter in **containers.conf**. -When all available locks are exhausted, no further containers and pods can be created until some existing containers and pods are removed. This can be avoided by increasing the number of locks available via modifying **libpod.conf** and subsequently running **podman system renumber** to prepare the new locks (and reallocate lock numbers to fit the new struct). +When all available locks are exhausted, no further containers and pods can be created until some existing containers and pods are removed. This can be avoided by increasing the number of locks available via modifying **containers.conf** and subsequently running **podman system renumber** to prepare the new locks (and reallocate lock numbers to fit the new struct). **podman system renumber** must be called after any changes to **num_locks** - failure to do so will result in errors starting Podman as the number of locks available conflicts with the configured number of locks. @@ -20,7 +20,7 @@ When all available locks are exhausted, no further containers and pods can be cr If possible, avoid calling **podman system renumber** while there are other Podman processes running. ## SEE ALSO -`podman(1)`, `libpod.conf(5)` +`podman(1)`, `containers.conf(5)` ## HISTORY February 2019, Originally compiled by Matt Heon (mheon at redhat dot com) |