1podman-system-renumber(1)()                        podman-system-renumber(1)()
2
3
4

NAME

6       podman-system-renumber  -  Migrate  lock  numbers to handle a change in
7       maximum number of locks
8
9

SYNOPSIS

11       podman system renumber
12
13

DESCRIPTION

15       podman system renumber renumbers locks used by containers and pods.
16
17
18       Each Podman container and pod is allocated a lock at creation time,  up
19       to  a  maximum number controlled by the num_locks parameter in contain‐
20       ers.conf.
21
22
23       When all available locks are exhausted, no further containers and  pods
24       can  be  created  until  some existing containers and pods are removed.
25       This can be avoided by increasing the number  of  locks  available  via
26       modifying containers.conf and subsequently running podman system renum‐
27       ber to prepare the new locks (and reallocate lock numbers  to  fit  the
28       new struct).
29
30
31       podman  system renumber must be called after any changes to num_locks -
32       failure to do so will result in errors starting Podman as the number of
33       locks available conflicts with the configured number of locks.
34
35
36       podman system renumber can also be used to migrate 1.0 and earlier ver‐
37       sions of Podman, which used a different  locking  scheme,  to  the  new
38       locking model. It is not strictly required to do this, but it is highly
39       recommended to do so as deadlocks can occur otherwise.
40
41
42       If possible, avoid calling podman system renumber while there are other
43       Podman processes running.
44
45

SEE ALSO

47       podman(1), containers.conf(5)
48
49

HISTORY

51       February  2019,  Originally  compiled by Matt Heon (mheon at redhat dot
52       com)
53
54
55
56                                                   podman-system-renumber(1)()