Fix memory-swap description in older API versions
A value of -1 disables the *limit* so enables unlimited swap Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 1c95b858ac040974d2be73bb31d0d59af9b0b960 Component: engine
This commit is contained in:
@ -207,8 +207,8 @@ Json Parameters:
|
||||
for the container.
|
||||
- **User** - A string value containing the user to use inside the container.
|
||||
- **Memory** - Memory limit in bytes.
|
||||
- **MemorySwap**- Total memory limit (memory + swap); set `-1` to disable swap,
|
||||
always use this with `memory`, and make the value larger than `memory`.
|
||||
- **MemorySwap** - Total memory limit (memory + swap); set `-1` to enable unlimited swap.
|
||||
You must use this with `memory` and make the swap value larger than `memory`.
|
||||
- **CpuShares** - An integer value containing the CPU Shares for container
|
||||
(ie. the relative weight vs other containers).
|
||||
- **Cpuset** - The same as CpusetCpus, but deprecated, please don't use.
|
||||
@ -1207,7 +1207,7 @@ Query Parameters:
|
||||
- **rm** - remove intermediate containers after a successful build (default behavior)
|
||||
- **forcerm** - always remove intermediate containers (includes rm)
|
||||
- **memory** - set memory limit for build
|
||||
- **memswap** - Total memory (memory + swap), `-1` to disable swap
|
||||
- **memswap** - Total memory (memory + swap), `-1` to enable unlimited swap.
|
||||
- **cpushares** - CPU shares (relative weight)
|
||||
- **cpusetcpus** - CPUs in which to allow execution, e.g., `0-3`, `0,1`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user