mirror of
https://github.com/containers/podman.git
synced 2025-12-13 02:09:16 +08:00
c9c2f644da
In each options/foo.md, keep a list of where the option is used. This will be valuable to anyone making future edits, and to those reviewing those edits. This may be a controversial commit, because those crossref lists are autogenerated as a side effect of the script that reads them. It definitely violates POLA. And one day, some kind person will reconcile (e.g.) --label, using it in more man pages, and maybe forget to git-commit the rewritten file, and CI will fail. I think this is a tough tradeoff, but worth doing. Without this, it's much too easy for someone to change an option file in a way that renders it inapplicable/misleading for some podman commands. Signed-off-by: Ed Santiago <santiago@redhat.com>
19 lines
849 B
Markdown
19 lines
849 B
Markdown
####> This option file is used in:
|
|
####> podman build, container clone, create, run, update
|
|
####> If you edit this file, make sure your changes
|
|
####> are applicable to all of those.
|
|
#### **--cpu-quota**=*limit*
|
|
|
|
Limit the CPU Completely Fair Scheduler (CFS) quota.
|
|
|
|
Limit the container's CPU usage. By default, containers run with the full
|
|
CPU resource. The limit is a number in microseconds. If a number is provided,
|
|
the container will be allowed to use that much CPU time until the CPU period
|
|
ends (controllable via **--cpu-period**).
|
|
|
|
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.
|