This repository was archived by the owner on Jul 28, 2024. It is now read-only.
Use digests for Docker images #1398
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: #1389
The
docker-compose.ymlfiles now contain specific digests like this:Dockerfiles also lock specific versions:
FROM wordpress:cli@sha256:f8600f5df710c0973ed250e16c1286de7f8344cd8ce0dcba3779931010e956d4This should lead to more predictable versions running on users' computers.
Implementation notes:
docker-compose config --resolve-image-digestsprints out docker-compose with digests resolved.image:tag@shais a nice trick from this article (that article is worth reading anyway!).