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
This inconsistent behaviour has actually been present since v0.10.0.
Depending on the title of the named targets, some may be omitted from the resulting group with no warning or error.
If default is not a valid name for a target, there should be a warning or error to that effect. Instead it silently ignores the target when processing bake files with multiple targets.
Contributing guidelines
I've found a bug and checked that ...
Description
If bake file contains a target named
default
the parsing behaviour is different for that target than other target names.This is apparent when processing the files with the
--print
option, and a default group is generated if one is not defined in the bake file.Expected behaviour
Versions
v0.9.1
and earlier correctly include all named targets in the default group.Actual behaviour
This inconsistent behaviour has actually been present since
v0.10.0
.Depending on the title of the named targets, some may be omitted from the resulting group with no warning or error.
If
default
is not a valid name for a target, there should be a warning or error to that effect. Instead it silently ignores the target when processing bake files with multiple targets.Buildx version
github.com/docker/buildx v0.19.1 5113f9e
Docker info
Builders list
Configuration
For the
multiarch
target we see a default group is created including the named target.For the
default
target we do not see any group get created.For the
default
andmultiarch
target in one command, we see the default group is created but thedefault
target has been omitted.Build logs
Additional info
No response
The text was updated successfully, but these errors were encountered: