You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
When using buildx with a tag but without a name, it incorrectly reports that a tag is needed.
This can lead to a lot of wasted time when debugging for example GitHub actions where environment variables may be used and one of them is set incorrectly.
The user now expects the environment variable for the tag being empty when in fact it is the name that is missing.
Expected behaviour
docker buildx build . --output type=image,push-by-digest=true,push=true,tag=123 should return:
Contributing guidelines
I've found a bug and checked that ...
Description
When using buildx with a tag but without a name, it incorrectly reports that a tag is needed.
This can lead to a lot of wasted time when debugging for example GitHub actions where environment variables may be used and one of them is set incorrectly.
The user now expects the environment variable for the tag being empty when in fact it is the name that is missing.
Expected behaviour
docker buildx build . --output type=image,push-by-digest=true,push=true,tag=123
should return:Actual behaviour
docker buildx build . --output type=image,push-by-digest=true,push=true,tag=123
results in:Buildx version
0.20.1
Docker info
Builders list
Configuration
No Dockerfile needed, this happens even when calling it in a directory without a Dockerfile.
Build logs
Additional info
This seems to be caused by
buildx/build/build.go
Line 360 in 2389d45
buildx/build/build.go
Line 547 in 2389d45
The text was updated successfully, but these errors were encountered: