Run the service image as an unprivileged user with a read-only root
The API image starts as root and writes temporary report files into the application directory.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Least privilege · Container hardening
Estimated field mix
- Security60%
- Platform engineering40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional reporting API is rebuilt separately for staging and production. Different dependency resolutions and mutable tags make incident rollback unreliable.
Setup prerequisites
- Create a tiny local HTTP service and nonprivileged image build.
- Use synthetic registries or provider fixtures; no production deployment.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Use a non-root runtime user.
- Keep the base filesystem read-only with an explicit temporary directory.
- Reject startup when required writable storage is unavailable.
Implementation constraints
- No privileged mode, host mounts, host networking or container-engine socket.
Verification to include
- Serve a request under the restricted runtime configuration.
- Attempt a write to the application directory and verify denial.
Deliverables
- Restricted runtime definition and filesystem probe
Rollout and recovery
Canary the restricted image locally; stop rollout if required writes lack an explicit temporary path.
Value of the work
For the engineer: Practice artifact identity, least privilege and reproducible delivery.
For the team: Review whether deployed bytes can be traced and rolled back reliably.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.