Pin Docker base image in Dockerfile#1
Open
atomista[bot] wants to merge 1 commit into
Open
Conversation
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
2 times, most recently
from
December 3, 2021 08:15
c0d33ce to
adfd3ea
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
from
December 21, 2021 20:12
adfd3ea to
11305a1
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
from
January 12, 2022 02:00
11305a1 to
78cdc77
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
3 times, most recently
from
February 2, 2022 08:00
c28fec9 to
5db2a42
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
2 times, most recently
from
March 5, 2022 00:12
5a41ab8 to
c630d77
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
from
March 22, 2022 09:48
c630d77 to
49e688c
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
2 times, most recently
from
March 31, 2022 02:36
7f969e0 to
c280e4b
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
2 times, most recently
from
April 22, 2022 07:24
f17416d to
7158ba4
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
3 times, most recently
from
May 18, 2022 09:24
8d6eca2 to
f7b6ac6
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
from
May 19, 2022 08:36
f7b6ac6 to
a63ae08
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
2 times, most recently
from
May 29, 2022 23:36
7beeb83 to
ec737ca
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
from
June 24, 2022 02:12
ec737ca to
57cadff
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
3 times, most recently
from
July 13, 2022 09:48
58c2786 to
8ee82ab
Compare
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
3 times, most recently
from
August 3, 2022 16:00
effd816 to
f12be53
Compare
node:14-buster-slim -> node:14-buster-slim@sha256:8e2b1bf00c319363441e3211806c126c7b53f4a9d4c2219f6924af2c7be78872 [atomist:generated] [atomist-skill:atomist/docker-base-image-policy] Signed-off-by: Atomist Bot <bot@atomist.com>
atomista
Bot
force-pushed
the
atomist/pin-docker-base-image/dockerfile
branch
from
August 23, 2022 22:36
f12be53 to
eb28e61
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
node:14-buster-sliminDockerfileto the current digest.atomist-docker-tutorial/Dockerfile
Line 1 in eb28e61
Digest
sha256:8e2b1bf00c319363441e3211806c126c7b53f4a9d4c2219f6924af2c7be78872references a multi-CPU architecture image manifest. This image supports the following architectures:sha256:fa40c6550d6a14b1445cc402928bddf3c6e29da66abeada993918d7ae905b037linux/amd64Pinning
FROMlines 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:
Dockerfile