mirror of
https://github.com/containers/podman.git
synced 2025-06-01 17:17:47 +08:00

When an unsupported limit on cgroups V1 rootless systems is requested, podman prints an warning message and ignores the option/flag. ``` Target options/flags: --cpu-period, --cpu-quota, --cpu-rt-period, --cpu-rt-runtime, --cpus, --cpu-shares, --cpuset-cpus, --cpuset-mems, --memory, --memory-reservation, --memory-swap, --memory-swappiness, --blkio-weight, --device-read-bps, --device-write-bps, --device-read-iops, --device-write-iops, --blkio-weight-device ``` Related to https://github.com/containers/podman/discussions/10152 Signed-off-by: Toshiki Sonoda <sonoda.toshiki@fujitsu.com>
13 lines
577 B
Markdown
13 lines
577 B
Markdown
#### **--cpu-period**=*limit*
|
|
|
|
Set the CPU period for the Completely Fair Scheduler (CFS), which is a
|
|
duration in microseconds. Once the container's CPU quota is used up, it will
|
|
not be scheduled to run until the current period ends. Defaults to 100000
|
|
microseconds.
|
|
|
|
On some systems, changing the resource limits may not be allowed for non-root
|
|
users. For more details, see
|
|
https://github.com/containers/podman/blob/main/troubleshooting.md#26-running-containers-with-resource-limits-fails-with-a-permissions-error
|
|
|
|
This option is not supported on cgroups V1 rootless systems.
|