Image Signing and Verification
What you'll learn: How to cryptographically sign container images and verify their integrity using Docker Content Trust and Notary.
The Core Problem
When you pull a container image from a registry, how do you know it hasn't been tampered with? What if an attacker replaced your trusted nginx:latest image with a malicious version? Without cryptographic signatures, you're trusting the registry blindly.
How Image Signing Works
Image signing is like sealing an envelope with wax and your personal stamp. When you build and push an image, you create a cryptographic signature using your private key. Anyone with your public key can verify that:
- The image came from you (authentication)
- Nobody modified it (integrity)
- You signed this specific version (non-repudiation)
Docker Content Trust and Notary
Docker Content Trust (DCT) is Docker's implementation of image signing, powered by Notary under the hood. Notary is a project that implements The Update Framework (TUF), providing secure distribution of trusted content.
When DCT is enabled, Docker refuses to pull unsigned images. The registry stores both the image layers and separate signature metadata. During a pull operation, Docker:
- Downloads the signature metadata
- Verifies it matches the image digest
- Checks the signature against trusted public keys
- Only proceeds if verification succeeds
This creates a chain of trust from the image publisher to the consumer, ensuring supply chain integrity even if the registry itself is compromised.
Key Takeaway: Image signing and verification using Docker Content Trust and Notary provides cryptographic proof that container images haven't been tampered with and come from trusted publishers, defending against supply chain attacks and registry compromises.