Content trust and image signing in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Enable Docker Content Trust and pull an image

What is the output when you run the following commands with Docker Content Trust enabled?

export DOCKER_CONTENT_TRUST=1
docker pull alpine:latest

Assume the image is signed and available.

Docker

export DOCKER_CONTENT_TRUST=1
docker pull alpine:latest

A

Pulling trust metadata
Error: trust data expired for alpine:latest

B Error: image verification failed: no trust data for alpine:latest

C

Pulling from library/alpine
Status: Image is unsigned, cannot pull

D

Pulling trust metadata
latest: Pulling from library/alpine
Digest: sha256:... 
Status: Downloaded newer image for alpine:latest

💡 Hint

Docker Content Trust verifies signatures before pulling images.

When DOCKER_CONTENT_TRUST=1 is set, Docker pulls trust metadata and verifies the image signature before downloading. If the image is signed and valid, it proceeds to pull the image.

🧠 Conceptual

intermediate

Purpose of Docker Content Trust

Which of the following best describes the main purpose of Docker Content Trust?

A To verify the integrity and publisher of Docker images using digital signatures

B To automatically update Docker images to the latest version

C To speed up Docker image downloads

D To encrypt Docker images during transfer

💡 Hint

Think about what 'trust' means in software distribution.

Docker Content Trust uses digital signatures to ensure images come from a trusted source and have not been tampered with.

❓ Troubleshoot

advanced

Troubleshooting image pull failure with content trust

You try to pull a signed image with Docker Content Trust enabled but get this error:

Error: remote trust data does not exist for docker.io/library/nginx:latest

What is the most likely cause?

A The image digest has changed but the signature was not updated

B Your Docker client version is too old to support content trust

C The image is unsigned or no trust data was published for this tag

D Your network connection is blocking Docker Hub

💡 Hint

The error mentions 'remote trust data does not exist'.

This error means the image does not have signed trust data published, so Docker cannot verify it with content trust enabled.

🔀 Workflow

advanced

Steps to sign a Docker image using Notary

What is the correct order of steps to sign a Docker image using Docker Content Trust and Notary?

A 3,1,2,4

B 1,2,3,4

C 1,3,2,4

D 3,2,1,4

💡 Hint

You need keys before pushing signed images.

First, you generate or load signing keys, then tag the image, push it with content trust enabled to sign it, and finally verify the signature.

✅ Best Practice

expert

Best practice for managing Docker Content Trust keys

Which practice is the most secure and recommended way to manage Docker Content Trust signing keys in a team environment?

A Share the root signing key file among all team members via email

B Store root keys in a secure hardware security module (HSM) or vault and use delegation keys for daily signing

C Keep all keys on a shared network drive accessible to the team

D Generate new root keys for each image push to avoid key reuse

💡 Hint

Think about limiting exposure of the most sensitive keys.

Root keys are highly sensitive and should be stored securely offline or in an HSM. Delegation keys allow safer daily signing without exposing root keys.

Practice

1. What is the main purpose of Docker content trust?

easy

A. To speed up Docker image downloads

B. To verify the authenticity and integrity of Docker images

C. To compress Docker images for storage

D. To automatically update Docker images

Solution

1. Step 1: Understand content trust concept

   Content trust in Docker is designed to ensure images are verified and safe to use by checking their signatures.

2. Step 2: Identify the purpose from options

   Only To verify the authenticity and integrity of Docker images mentions verifying authenticity and integrity, which matches content trust's goal.

3. Final Answer:

   To verify the authenticity and integrity of Docker images -> Option B

4. Quick Check:

   Content trust = verify image authenticity [OK]

Hint: Content trust means verifying image signatures before use [OK]

Common Mistakes:

• Confusing content trust with image compression
• Thinking content trust speeds up downloads
• Assuming content trust auto-updates images

2. Which command correctly enables Docker content trust before pulling an image?

easy

A. set DOCKER_CONTENT_TRUST=1 docker pull alpine

B. docker pull --trust alpine

C. export DOCKER_CONTENT_TRUST=1 && docker pull alpine

D. docker pull alpine --enable-content-trust

Solution

1. Step 1: Recall how to enable content trust

   Content trust is enabled by setting the environment variable DOCKER_CONTENT_TRUST=1 before running docker pull.

2. Step 2: Match correct syntax

   export DOCKER_CONTENT_TRUST=1 && docker pull alpine uses the correct shell syntax to export the variable and then pull the image.

3. Final Answer:

   export DOCKER_CONTENT_TRUST=1 && docker pull alpine -> Option C

4. Quick Check:

   Set env var DOCKER_CONTENT_TRUST=1 before pull [OK]

Hint: Use export DOCKER_CONTENT_TRUST=1 before docker pull [OK]

Common Mistakes:

• Using incorrect flags like --trust or --enable-content-trust
• Trying to set env var inline without export
• Confusing Windows and Linux environment variable syntax

3. What will happen if you run docker pull alpine with DOCKER_CONTENT_TRUST=1 set but the image is unsigned?

medium

A. The image will be pulled without verification

B. Docker will automatically sign the image locally

C. Docker will pull the image but warn about missing signature

D. Docker will refuse to pull the image and show an error

Solution

1. Step 1: Understand content trust behavior on unsigned images

   When content trust is enabled, Docker requires a valid signature to pull an image.

2. Step 2: Identify expected Docker response

   If the image is unsigned, Docker refuses to pull it and shows an error to prevent unverified usage.

3. Final Answer:

   Docker will refuse to pull the image and show an error -> Option D

4. Quick Check:

   Content trust blocks unsigned image pulls [OK]

Hint: Content trust blocks unsigned images from pulling [OK]

Common Mistakes:

• Thinking Docker pulls unsigned images anyway
• Assuming Docker signs images automatically
• Believing Docker only warns but allows pull

4. You enabled content trust but get an error: no trust data available when pulling an image. What is the likely cause?

medium

A. The image has no signed tags in the registry

B. Docker daemon is not running

C. You forgot to set DOCKER_CONTENT_TRUST=0

D. Your internet connection is down

Solution

1. Step 1: Analyze the error message meaning

   'No trust data available' means Docker cannot find signed metadata for the image tags in the registry.

2. Step 2: Match cause to options

   The image has no signed tags in the registry correctly states the image lacks signed tags, causing this error when content trust is enabled.

3. Final Answer:

   The image has no signed tags in the registry -> Option A

4. Quick Check:

   No trust data = no signed tags in registry [OK]

Hint: No trust data means image tags are unsigned [OK]

Common Mistakes:

• Assuming Docker daemon stopped causes this error
• Thinking DOCKER_CONTENT_TRUST=0 fixes error when trust is needed
• Blaming internet connection without checking image signing

5. You want to ensure only signed images are deployed in your production environment. Which approach best achieves this?

hard

A. Set DOCKER_CONTENT_TRUST=1 on all production servers and pull images normally

B. Manually verify image signatures after pulling unsigned images

C. Disable content trust and rely on image tags naming conventions

D. Use docker pull --no-trust to skip signature checks

Solution

1. Step 1: Identify how to enforce signed image usage

   Setting DOCKER_CONTENT_TRUST=1 forces Docker to only pull images with valid signatures, blocking unsigned ones.

2. Step 2: Evaluate options for production safety

   Set DOCKER_CONTENT_TRUST=1 on all production servers and pull images normally correctly enforces signature verification automatically on production servers.

3. Final Answer:

   Set DOCKER_CONTENT_TRUST=1 on all production servers and pull images normally -> Option A

4. Quick Check:

   Enable content trust to enforce signed images [OK]

Hint: Enable DOCKER_CONTENT_TRUST=1 in production for safety [OK]

Common Mistakes:

• Trying to verify signatures manually after pull
• Disabling content trust and trusting tags only
• Using flags to skip trust checks in production