A production container is found running with `--privileged` mode enabled, and nobody on the current team remembers why.
This is a significant, likely unnecessary security exposure — `--privileged` grants nearly all host capabilities and device access, far beyond what almost any application legitimately needs. Investigate whether it was added to work around a specific narrower requirement (e.g., needing a particular capability or device access) that could instead be granted via a scoped `--cap-add` or specific `--device` flag, and remove the blanket privileged flag once the actual minimal requirement is identified and substituted.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response