Skip to main content
PreparationZone Logo
PrepZone

Non-Root Users, Scanning, and SBOMs

Run as non-root, read-only filesystems, Trivy scans, and software bill of materials.

Pass checkpoint below

Why this matters

  • This topic directly affects how reliably BookStore reaches production — hardening shrinks attack surface.
  • Interviewers connect hands-on commands and manifests to real delivery stories, not buzzwords.
  • Later modules assume you can explain both the why and the concrete file or command involved.
  • Platform maturity shows up when teams automate this instead of relying on tribal knowledge.
Virtual Machine
App AGuest OS
HypervisorFull OS per VM
Host OS + Hardware
Container
App AContainer
App BContainer
Container runtimeShared kernel
Host OS + Hardware
VMs virtualise hardware; containers share the host kernel and isolate with namespaces and cgroups.

Non-root and minimal base

Reduce CVE surface: BookStore engineers treat this as part of the standard path from laptop to docker security hardening readiness. Document decisions in the team runbook so on-call knows which knobs exist.

Key ideas

  • Non-root and minimal base — primary idea for docker-security-hardening
  • BookStore context — catalog API, checkout, and inventory services share the same pattern
  • Automation — prefer pipeline jobs over manual SSH steps
  • Verification — staging must prove the change before prod traffic

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 2 sections

  • Scan in CI
  • Production checklist

Test yourself

Answer these before moving on — recall is what makes it stick.