Running Sandboxed Chromium in Docker Is Possible Without --no-sandbox
The widespread advice to use Chromium's --no-sandbox flag in Docker containers is a security shortcut that disables the browser's primary defense against malicious content. Vitalii, founder of PDF-rendering service PDFik, reveals that hardened containers running non-root, capability-dropped configurations can still operate with Chromium's sandbox enabled. Chromium uses two separate sandbox mechanisms — a legacy setuid helper and a namespace-based layer — and only the former is blocked in locked-down containers. A security audit of PDFik's own infrastructure incorrectly flagged sandbox support as impossible, unaware that the namespace-based sandbox had been functioning in production all along. The episode highlights how repeated tutorial folklore about --no-sandbox has obscured the distinction between Chromium's two sandboxing methods, leading to unnecessary security compromises.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in