mirror of
https://github.com/containers/podman.git
synced 2025-06-03 20:33:20 +08:00
050f3291b9
podman update allows users to change the cgroup configuration of an existing container using the already defined resource limits flags from podman create/run. The supported flags in crun are: this command is also now supported in the libpod api via the /libpod/containers/<CID>/update endpoint where the resource limits are passed inthe request body and follow the OCI resource spec format –memory –cpus –cpuset-cpus –cpuset-mems –memory-swap –memory-reservation –cpu-shares –cpu-quota –cpu-period –blkio-weight –cpu-rt-period –cpu-rt-runtime -device-read-bps -device-write-bps -device-read-iops -device-write-iops -memory-swappiness -blkio-weight-device resolves #15067 Signed-off-by: Charlie Doern <cdoern@redhat.com>
12 lines
551 B
Markdown
12 lines
551 B
Markdown
#### **--memory-reservation**=*number[unit]*
|
|
|
|
Memory soft limit. A _unit_ can be **b** (bytes), **k** (kibibytes), **m** (mebibytes), or **g** (gibibytes).
|
|
|
|
After setting memory reservation, when the system detects memory contention
|
|
or low memory, containers are forced to restrict their consumption to their
|
|
reservation. So you should always set the value below **--memory**, otherwise the
|
|
hard limit will take precedence. By default, memory reservation will be the same
|
|
as memory limit.
|
|
|
|
This option is not supported on cgroups V1 rootless systems.
|