Skip to content

How to harden a ClickHouse container (and is clickhouse:24.8 safe for untrusted workloads?)

Short answer: a stock docker run clickhouse:24.8 is not a boundary you should trust around untrusted code or an untrusted network. Graded on IronClaw's seven-dimension containment scale, the default configuration scores 48 of 100, grade D (porous). Higher is safer. Four runtime flags take the same image to 100 of 100, grade A. This guide shows the exact gaps and the exact fixes, straight from the scan data.

Every number here comes from a read-only docker inspect of clickhouse:24.8, the same data behind its isolation scorecard. No workload is executed. How scoring works →

Where the default configuration leaks

ironctl scan grades seven independent containment boundaries. On a default docker run clickhouse:24.8, four of them fail or warn:

Dimension Verdict Score What the scan found
Non-root user (uid != 0) ❌ FAIL 0/15 runs as root (uid 0); a container escape starts with host-uid 0
Dropped capabilities ❌ FAIL 4/20 default capability set retained (CAP_NET_RAW, CAP_MKNOD, and more)
Seccomp profile ✅ PASS 15/15 seccomp profile active
Network isolation / egress ⚠️ WARN 4/15 network=bridge: outbound egress is possible
Read-only root filesystem ❌ FAIL 0/10 root filesystem is writable
No docker.sock exposure ✅ PASS 15/15 no control socket mounted
No shared host namespaces ✅ PASS 10/10 no host PID/IPC/network sharing

For an analytics database, the two that should worry you most are egress and root. A ClickHouse process holds your whole event history in queryable columns; one that can reach the network can ship it out the moment a URL-table function, a dictionary source, or an HTTP handler CVE lands code execution. And a root process that escapes the container escapes as root on the host.

Harden it: the exact --fix remediation

ironctl scan my-clickhouse --fix prints one remediation per failed dimension, then assembles a single copy-pasteable hardened run. For clickhouse:24.8 the prescription is:

  • --cap-drop=ALL (Dropped capabilities, +16): drop every Linux capability; add back only what the workload provably needs. ClickHouse itself needs none of the defaults.
  • --user 65532:65532 (Non-root user, +15): pin a non-root uid so an escape does not begin as host uid 0. Point the data directory at a volume this uid owns.
  • --network=none (Network isolation, +11): if the database is only reached by services on a private user-defined network, cut host egress entirely; otherwise attach a single internal network with no default route, not bridge. ClickHouse's remote table functions are exactly the reach you want to close.
  • --read-only --tmpfs /tmp (Read-only rootfs, +10): make the root filesystem read-only and mount /var/lib/clickhouse as an explicit writable volume. Removes the persistence surface.

Before and after

# Before: 48/100, grade D
docker run -d --name clickhouse clickhouse:24.8

# After: 100/100, grade A
docker run -d --name clickhouse-hardened \
  --user 65532:65532 \
  --cap-drop=ALL \
  --security-opt=no-new-privileges \
  --read-only --tmpfs /tmp \
  -v clickhouse-data:/var/lib/clickhouse \
  --network=none \
  clickhouse:24.8

Rescan and the same seven dimensions all pass: ironctl scan clickhouse-hardened reports 100/100 grade A. That is a 52-point swing from four one-line flags, no image rebuild.

Verify it on your own database

The grade above is the default image. Your deployment is what matters. Scan it in ten seconds:

# install (Homebrew)
brew install ironsecco/ironclaw/ironclaw

# grade your running container, then print the fixes
ironctl scan my-clickhouse
ironctl scan my-clickhouse --fix

ironctl scan also reads a docker-compose.yml service or a Kubernetes manifest, so you can grade the ClickHouse in your stack, not just a bare docker run.

Keep going