SV-235806r627545_rule
V-235806
SRG-APP-000141
DKER-EE-002010
CAT II
10
Document container memory requirements in the System Security Plan (SSP).
Run the container with only as much memory as required. Always run the container using the --memory argument.
For example, run a container as below:
docker run --interactive --tty --memory 256m centos /bin/bash
In the above example, the container is started with a memory limit of 256 MB.
Note: The output of the below command would return values in scientific notation if memory limits are in place.
docker inspect --format='{{.Config.Memory}}' 7c5a2d4c7fe0
For example, if the memory limit is set to 256 MB for the above container instance, the output of the above command would be 2.68435456e+08 and NOT 256m. Convert this value using a scientific calculator or programmatic methods.
Ensure memory limits are in place for all containers.
This check should be executed on all nodes in a Docker Enterprise cluster.
via CLI:
Linux: As a Docker EE Admin, execute the following command using a Universal Control Plane (UCP) client bundle:
docker ps --quiet --all | xargs docker inspect --format '{{ .Id }}: Memory={{ .HostConfig.Memory }}'
If the above command returns 0, it means the memory limits are not in place and this is a finding.
V-235806
False
DKER-EE-002010
Ensure memory limits are in place for all containers.
This check should be executed on all nodes in a Docker Enterprise cluster.
via CLI:
Linux: As a Docker EE Admin, execute the following command using a Universal Control Plane (UCP) client bundle:
docker ps --quiet --all | xargs docker inspect --format '{{ .Id }}: Memory={{ .HostConfig.Memory }}'
If the above command returns 0, it means the memory limits are not in place and this is a finding.
M
5281