This repository has been archived by the owner on Oct 29, 2024. It is now read-only.
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 re-pins the Docker base image
busybox:1.35.0
inDockerfile
to the current digest.volumes-backup-extension/Dockerfile
Line 48 in 9ba92c8
Digest
sha256:d7f4aada301c0f13d93ceed62fef318c195c38bf430fc8bfbdf1d850514422ff
references a multi-CPU architecture image manifest. This image supports the following architectures:sha256:f1d6d77ed9ca269e850013ce6d5d73aef0c737d291bbc573e6da6245c49d62ea
linux/ppc64le
Changelog for
busybox:1.35.0
Commit
New image build caused by commit docker-library/official-images@94a73bc to
library/busybox
:Comparison
Comparing Docker image
busybox:1.35.0
at digestsCurrent
sha256:80548a8d85fa32ce25b126657e29e6caf92ce8aa6b4a0bb5708c58a8d6a751f3
andProposed
sha256:d7f4aada301c0f13d93ceed62fef318c195c38bf430fc8bfbdf1d850514422ff
:Packages
No package differences detected
Files
No file modifications detected
History
The following differences in
docker history
were detected:Ports
No different exposed ports detected
Environment Variables
No different environment variables detected
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:
Dockerfile