Docker Resource Management Concepts: Difference between revisions
Jump to navigation
Jump to search
m (Ovidiu moved page Docker Resources Management Concepts to Docker Resource Management Concepts without leaving a redirect) |
|||
(4 intermediate revisions by the same user not shown) | |||
Line 5: | Line 5: | ||
=Internal= | =Internal= | ||
* [[Kubernetes | * [[Kubernetes Resource Management Concepts]] | ||
* [[Java in a Container]] | * [[Java in a Container]] | ||
Line 29: | Line 29: | ||
Also see: {{Internal|Linux_cgroups#Controlling_CPU_Throttling|cgroups - Controlling CPU Throttling}} | Also see: {{Internal|Linux_cgroups#Controlling_CPU_Throttling|cgroups - Controlling CPU Throttling}} | ||
==User Memory Constraints== | |||
* https://docs.docker.com/engine/reference/run/#user-memory-constraints | |||
Also see: {{Internal|Linux_cgroups#Memory_Limit|CGroups Memory Limit}} | |||
=Organizatorium= | =Organizatorium= | ||
* Docker switches (-m, -memory and -memory-swap) instruct the Linux kernel to kill the process running inside a container if it tries to exceed the specified limit. | * Docker switches (-m, -memory and -memory-swap) instruct the Linux kernel to kill the process running inside a container if it tries to exceed the specified limit. |
Latest revision as of 18:31, 25 August 2020
External
Internal
Overview
The docker runtime will kill a process that it is attempting to exceed the resource limits, such as memory specified with -m.
The resource usage statistics for running containers can be displayed with:
docker stats
Controlling CPU
Also see:
CPU Quota Constraint
Also see:
User Memory Constraints
Also see:
Organizatorium
- Docker switches (-m, -memory and -memory-swap) instruct the Linux kernel to kill the process running inside a container if it tries to exceed the specified limit.