Menu

I pinned every image by digest. That froze 97 vulnerabilities in place.
📰

I pinned every image by digest. That froze 97 vulnerabilities in place.

DEV Community: docker·samuel mbabhazi·about 2 hours ago
#qQO8amga
#devtodocker#devto#dev#postgresql#caddy
Reading 0:00
15s threshold

Shipkeep is an open-source platform to deploy apps on your own servers. The control plane runs as a Docker Compose stack: the control plane image, PostgreSQL and Caddy.

Every image in that stack is pinned by digest. Every GitHub Action is pinned to a commit. CI runs CodeQL, Semgrep, gosec, gitleaks, and a Trivy scan of the repository. All green, every day.

This week I pointed Trivy at what an installation actually runs, the images, instead of at the repository. The PostgreSQL image alone had 97 fixable high or critical findings.

Pinning freezes the fixes out

Pinning by digest is the right call for a supply chain: a tag can be moved to anything, a digest cannot. But a digest also means the image never changes. Not when someone pushes something malicious to the tag, and not when Debian or the PostgreSQL project ships a fix.

The pin was set when the stack was written. The world kept patching.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.