Handle case where a dangling image is built, and an older SHA is matched during a docker build #140
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.
I have a problem where the buildAndTag function is failing. It succeeds to build, but fails to tag, because the image ID is not extracted correctly (in my case), because an older SHA is being matched.
My docker buildx version is:
github.com/docker/buildx v0.16.2-desktop.1 081c21b9e461293ae243a1ff813a680a4f5f8fb9=
The command that gets run is this:
docker buildx build --no-cache=false --rm=true --platform=linux/amd64 --progress=plain --load --file Dockerfile target/docker
This is the output I get:
sbt-docker then matches on the older "exporting config sha256" string instead of "naming to moby-dangling@sha256" string.