Pin Docker base image in mappingPipeline/Dockerfiles_legacy/Dockerfile #5
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.
This pull request pins the Docker base image
ubuntu:18.04
inmappingPipeline/Dockerfiles_legacy/Dockerfile
to the current digest.DESTv2/mappingPipeline/Dockerfiles_legacy/Dockerfile
Line 1 in 2a0dedb
Digest
sha256:8aa9c2798215f99544d1ce7439ea9c3a6dfd82de607da1cec3a8a2fae005931b
references a multi-CPU architecture image manifest. This image supports the following architectures:sha256:0779371f96205678dbcaa3ef499be2e5f262c8b09aadc11754bf3daf9f35e03e
linux/amd64
Pinning
FROM
lines to digests makes your builds repeatable. Atomist will raise new pull requests whenever the tag moves, so that you know when the base image has been updated. You can follow a new tag at any time. Just replace the digest with the new tag you want to follow. Atomist, will switch to following this new tag.File changed:
mappingPipeline/Dockerfiles_legacy/Dockerfile