Skip to content
This repository was archived by the owner on Jul 28, 2024. It is now read-only.

Conversation

@borekb
Copy link
Member

@borekb borekb commented Mar 10, 2019

Issue: #1389

The docker-compose.yml files now contain specific digests like this:

services:
  wordpress:
    image: versionpress/wordpress:php7.2-apache@sha256:64b3c10adfef9ae65a140d5547d670d996c5c852b9a840c71a86a5be4f777fdc

Dockerfiles also lock specific versions:

FROM wordpress:cli@sha256:f8600f5df710c0973ed250e16c1286de7f8344cd8ce0dcba3779931010e956d4

This should lead to more predictable versions running on users' computers.

Implementation notes:

  • docker-compose config --resolve-image-digests prints out docker-compose with digests resolved.
  • Using image:tag@sha is a nice trick from this article (that article is worth reading anyway!).
  • (BTW, the article is by Renovate, a tool that we should consider in the future.)

@borekb borekb added the scope: dev-infrastructure Build scripts, IDE settings, CI, Docker dev stack, testing, tooling, etc. label Mar 10, 2019
@borekb borekb added this to the 4.0 milestone Mar 10, 2019
@borekb borekb self-assigned this Mar 10, 2019
@borekb borekb changed the title Use Docker image digests to lock specific versions Use digests for Docker images Mar 10, 2019
@borekb borekb merged commit 29fa978 into master Mar 10, 2019
@borekb borekb deleted the 1389-image-digests branch March 10, 2019 22:36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

scope: dev-infrastructure Build scripts, IDE settings, CI, Docker dev stack, testing, tooling, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants