Image Vulnerability Scanning

Introduction

Every image you build inherits the vulnerabilities of its base layers and dependencies. Scanning tools find known CVEs so you can patch before attackers exploit.

Purpose of this lesson

This lesson teaches Image Vulnerability Scanning as an engineering decision: what problem it solves, when to use it, how to implement it safely, and what signals tell you it is failing.

Understanding the topic

Use this in production readiness work. These practices decide whether containers are merely running or are actually secure, observable, recoverable, and safe to promote through a delivery pipeline.

Core concepts to understand:

• Docker Scout (built into Docker Desktop) — easiest.
• Trivy — open source, fast, very popular.
• Grype, Snyk, Anchore — alternatives.
• Wire into CI to fail builds on critical CVEs.

Visual explanation

Architecture or command flow to keep in mind:

# Trivy on the command line
trivy image myorg/api:1.2.3

# In GitHub Actions
- uses: aquasecurity/trivy-action@master
  with:
    image-ref: myorg/api:1.2.3
    severity: CRITICAL,HIGH
    exit-code: 1

Step-by-step explanation

1. Define the production risk first: credential leakage, vulnerable base image, runaway resource use, missing logs, or broken delivery flow.
2. Apply the smallest control that reduces the risk: non-root user, read-only filesystem, scan gate, secret mount, limit, or log driver.
3. Prove the control with commands such as docker inspect, docker history, docker stats, and a failing test case.
4. Automate the check in CI or operational runbooks so it does not depend on memory.
5. Review the result after a real incident or release and tighten the policy where evidence shows gaps.

Informative example

Use the example below as a working baseline, then verify the runtime behavior instead of assuming the command or file is correct.

# Trivy on the command line
trivy image myorg/api:1.2.3

# In GitHub Actions
- uses: aquasecurity/trivy-action@master
  with:
    image-ref: myorg/api:1.2.3
    severity: CRITICAL,HIGH
    exit-code: 1

A production-minded check usually includes docker ps, docker logs, docker inspect, and one validation from outside the container such as curl, a database connection, or a registry pull.

# Verification loop for Image Vulnerability Scanning
docker ps -a
docker logs --tail=100 <container-name>
docker inspect <container-or-image-name>
docker system df

Real-world use

Stripe, Shopify and most security-conscious orgs gate every PR on a clean Trivy scan. New CVE published? Pipeline goes red automatically.

Enterprise use cases

In a mature engineering organization, Image Vulnerability Scanning is documented as a repeatable pattern with approved base images, ownership labels, CI checks, security expectations, rollback notes, and troubleshooting commands. The difference between a tutorial and production practice is that every container decision must be observable, reviewable, and reversible.

Best practices

• Scan on every build; fail on critical/high.
• Update base images monthly — they get patches too.

Common mistakes

• Scanning once and forgetting — new CVEs ship daily.

Debugging tips

• Inspect effective runtime settings with docker inspect; do not assume the Dockerfile or Compose file applied as expected.
• For resource incidents, compare docker stats, exit codes, OOMKilled state, and host memory pressure.
• For supply-chain issues, trace the exact image digest from build logs to registry to deployment.

Optimization strategies

• Treat image size, CVE count, non-root execution, and digest pinning as release quality signals.
• Set log rotation and resource limits before the first production incident, not after disk or memory exhaustion.
• Cache builds by registry or CI cache backend while still scanning the final pushed image.

Advanced interview questions

Hands-on exercise

Create a small lab for Image Vulnerability Scanning: run the example, inspect the created Docker object, intentionally introduce one mistake, and record the command that reveals the failure. The goal is not just to make the happy path work; it is to build operational reflexes.

# Hands-on lab scaffold
mkdir -p docker-image-vulnerability-scanning-lab
cd docker-image-vulnerability-scanning-lab

# Add the Dockerfile, compose.yml, or command from this lesson.
# Then run one happy-path test and one broken-path test.
docker version
docker info
docker system df

Summary

Image Vulnerability Scanning matters because Docker is not only a packaging tool; it is a runtime, build, networking, storage, and delivery workflow. Treat each lesson as a production habit: make it repeatable, inspectable, secure, and easy to debug.