Mount a Read-Only Root Filesystem
A writable container filesystem lets an attacker who reaches RCE drop a binary, rewrite the entrypoint, and persist until the next restart. A read-only root with named writable paths keeps normal operation while removing that persistence.
Procedure
- Run with the root read-only and give back only what the app needs:
docker run --read-only --tmpfs /tmp:rw,noexec,nosuid,size=64m --tmpfs /run app:x. - In Kubernetes:
securityContext: readOnlyRootFilesystem: true volumeMounts: - { name: tmp, mountPath: /tmp } - { name: cache, mountPath: /var/cache/app } volumes: - { name: tmp, emptyDir: {} } - { name: cache, emptyDir: {} } - Find what the app writes: run it read-only once and collect the
EROFSerrors:docker run --read-only app:x 2>&1 | grep -i 'read-only file system'. - For each path named, mount an
emptyDir(orpersistentVolumeClaimfor durable data). List grows only by observed need. - Use
noexec,nosuidon tmpfs mounts so anything dropped in/tmpcannot be executed. - Pin the app's temp and cache dirs via env so it does not guess:
TMPDIR=/tmp,XDG_CACHE_HOME=/var/cache/app. - Some runtimes write next to the binary (e.g. a
.pidfile in/app); either change the path or mount/app/runwritable.
Pitfalls
- Mounting a single writable dir over a path the image expected to contain files hides the baked content;
emptyDirstarts empty, so/app/templatesmounted writable loses the templates. readOnlyRootFilesystem: truebreaks images that write a lock file at/app/.lock(Go, some Node tooling) at startup, causing a crash loop that looks unrelated.- Tmpfs counts against the container memory limit; a
/tmpmounted withoutsize=can consume the whole limit and OOM the app. noexecon the path a launcher needs (e.g. extracted native libs) prevents JIT/extract-to-tmp from running; carve out a separateexecmount only if genuinely required.- A read-only root does not make mounted secrets read-only — a writable secret volume can still be tampered with; mount secrets with
defaultMode: 0400andreadOnly: true. - Entry points that
apt-get installat runtime fail immediately; install at build time. - Setting the flag cluster-wide without the
emptyDirs turns a working deploy into a CrashLoopBackOff across all replicas at once.
Verification
docker run --rm --read-only app:x sh -c 'touch /probe && echo writable || echo readonly'
# readonly
The probe write to the root fails while the app still serves traffic. Report the read-only root status and the writable mounts that were added.