fix: skaffold's assumption for image tag when building via buildkit and custom output #7120
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.
Fixes: #7024
Description
The original issue is about using local docker buildkit build. When building with buildkit and custom output, image is not tagged by default. Empty image id is passed to
ImageAPIClient.ImageTag
from the docker package, which fails.This line suggests that an empty image id is a valid use case in some circumstances.
I simply added a new condition to the method - if image id is empty, docker
ImageTag
is not called and simply returns empty string instead.Unit test included.
User facing changes (remove if N/A)
Before
When using buildkit and custom output, skaffold returned the following error
Error parsing reference: "" is not a valid repository/tag: invalid reference format
After
When using buildkit and custom output, skaffold successfully completes build.
Custom output is produced in both cases, as it's exported by the docker cli, not by skaffold