Omarchy Handed Every User Process Root Via Default Docker Group

Omarchy, the Linux distribution from DHH, shipped a default configuration that put its primary user in the docker group. Because the Docker daemon runs as root and listens on a socket that group members can talk to, any process in the user’s session could ask the daemon to spawn a root container, mount the host filesystem, and act on it as root — no password, sudo, or prompt required. A trivial proof of concept reads /etc/shadow by launching an Alpine container with the host root bind-mounted in.

The severity comes from scope and inheritance. Supplementary group membership propagates to child processes, so essentially everything running under the user’s session — browsers, editors, IDEs, npm scripts, and AI coding agents — inherited a direct path to full machine compromise. Any single application compromise became total. Worse, the setting was opt-out and applied even to users who never touched Docker, while the docs described it as running Docker “not as root,” language that reads almost backwards from the actual risk and could suggest a rootless setup that was never in place.

The flaw was privately disclosed and patched in 4.0.1 (3.x releases including 3.8.4 were also affected); the fix simply removes docker group membership from the default. The author credits the fast response but says it reinforces a broader lesson: developer-focused distributions carry outsized security responsibility because developer machines are high-value supply-chain targets that already accumulate credentials and disabled guardrails. As a mitigation, they recommend Podman, which is daemonless and runs containers as unprivileged, user-namespaced child processes with no root access at all.