Ensure that the container's root filesystem is mounted as read only

MediumLevel 1Automateddocker

Description

A read-only root filesystem stops attackers from modifying the container's binaries and configuration at runtime. The audit inspects every running container (docker ps -q) and prints the offending names; a host with no running containers is compliant.

How it is checked

Audit method: Shell command

shell

ids=$(docker ps -q) || exit 1; [ -z "$ids" ] && { echo compliant; exit 0; }; out=$(docker inspect --format '{{.Name}} {{.HostConfig.ReadonlyRootfs}}' $ids) || exit 1; bad=$(printf '%s\n' "$out" | awk '$2!="true"{print $1}'); [ -z "$bad" ] && echo compliant || printf '%s\n' "$bad"

Expected output: compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Redeploy with --read-only (compose: 'read_only: true') and use volumes or --tmpfs for directories that must be writable.

Properties

Operating systems: Any
Tags: dockerruntime
Reference: CIS Docker Benchmark v1.9.0 - 5.13 Ensure that the container's root filesystem is mounted as read only

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

shell

tmaegis scan --target docker