mirror of
https://github.com/containers/podman.git
synced 2025-06-13 19:52:11 +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>
16 lines
813 B
Markdown
16 lines
813 B
Markdown
####> This option file is used in:
|
|
####> podman build, container clone, create, pod clone, pod create, run, update
|
|
####> If you edit this file, make sure your changes
|
|
####> are applicable to all of those.
|
|
#### **--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.
|