Features

Configuration and Dockerfile The better base image, and the line to change

scancontainer reviews how a container image is built and configured, and points to the Dockerfile instruction behind each problem.

What it finds

  • Images that run as root, exposed ports and a missing HEALTHCHECK
  • Remote ADD, curl piped to a shell, ONBUILD and unpinned base images
  • Secrets in environment variables, deleted layers or build history
  • Build tools and unneeded packages left in production
  • Weak binary hardening: PIE, RELRO, stack canary and NX
  • Software installed when the container starts

What you get

  • A recommended base image, with the problems that disappear when you switch
  • The Dockerfile instruction that introduces each problem
  • A proposal for a smaller image: which files and packages are not needed
  • Licences and end-of-support dates for what you ship

What makes it different

Advice is tied to your Dockerfile, line by line, and the recommended base image comes with verified provenance.

Which plan includes it

Skipper and above. Compare plans.

FAQ

Questions about this feature

Which benchmarks do you check?

The CIS checks for container images and the NSA/CISA hardening guidance.

Do you need my Dockerfile?

No. The build history inside the image is enough to point to the instruction.

More features

Scan yours before the next deploy.