mirror of
https://github.com/containers/podman.git
synced 2025-09-19 12:56:57 +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
606 B
Markdown
12 lines
606 B
Markdown
#### **--memory**, **-m**=*number[unit]*
|
|
|
|
Memory limit. A _unit_ can be **b** (bytes), **k** (kibibytes), **m** (mebibytes), or **g** (gibibytes).
|
|
|
|
Allows the memory available to a container to be constrained. If the host
|
|
supports swap memory, then the **-m** memory setting can be larger than physical
|
|
RAM. If a limit of 0 is specified (not using **-m**), the container's memory is
|
|
not limited. The actual limit may be rounded up to a multiple of the operating
|
|
system's page size (the value would be very large, that's millions of trillions).
|
|
|
|
This option is not supported on cgroups V1 rootless systems.
|