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 will read a Dockerfile from STDIN without context. Due to the lack of a
context, no contents of any local directory will be sent to the Docker daemon.
Since there is no context, a Dockerfile ADD only works if it refers to a
remote URL.
There does not appear to be any similar way to request a null build context for a bake target. I am aware that other enhancements to the build system (ie only sending files from context when referenced by a COPY command) have made this largely unnecessary, but it would be nice to be able to explicitly request an empty/null context for the target.
Expected behaviour
Able to set a null context for the target.
Actual behaviour
cannot set an empty target. Null or empty string for the context are translated to the default ., and use of - is rejected with context from stdin not allowed in bake
Contributing guidelines
I've found a bug and checked that ...
Description
When using the legacy builder, you could read the Dockerfile from stdin to avoid sending any build context:
https://github.com/docker/cli/blob/24.0/docs/reference/commandline/build.md?plain=1#L267-L270
There does not appear to be any similar way to request a null build context for a bake target. I am aware that other enhancements to the build system (ie only sending files from context when referenced by a COPY command) have made this largely unnecessary, but it would be nice to be able to explicitly request an empty/null context for the target.
Expected behaviour
Able to set a null context for the target.
Actual behaviour
cannot set an empty target. Null or empty string for the
context
are translated to the default.
, and use of-
is rejected withcontext from stdin not allowed in bake
Buildx version
github.com/docker/buildx v0.16.0 10c9ff9
Docker info
Builders list
Configuration
Build logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: