Tonis Tiigi
9c7b9628ef
Currently there is no way to completely suppress the progress output. We have --progress=quiet but it has additional effect of printing image ID as a progress for historical reasons. --progress=none behaves like quiet but without this extra output printing depending on build output. Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
1.9 KiB
1.9 KiB
docker buildx dial-stdio
docker buildx dial-stdio [OPTIONS] < in.fifo > out.fifo &
Proxy current stdio streams to builder instance
Options
| Name | Type | Default | Description |
|---|---|---|---|
--builder |
string |
Override the configured builder instance | |
-D, --debug |
bool |
Enable debug logging | |
--platform |
string |
Target platform: this is used for node selection | |
--progress |
string |
none |
Set type of progress output (auto, plain, rawjson, tty). Use plain to show container output |
Description
dial-stdio uses the stdin and stdout streams of the command to proxy to the configured builder instance. It is not intended to be used by humans, but rather by other tools that want to interact with the builder instance via BuildKit API.
Examples
Example go program that uses the dial-stdio command wire up a buildkit client. This is, for example, use only and may not be suitable for production use.
client.New(ctx, "", client.WithContextDialer(func(context.Context, string) (net.Conn, error) {
c1, c2 := net.Pipe()
cmd := exec.Command("docker", "buildx", "dial-stdio")
cmd.Stdin = c1
cmd.Stdout = c1
if err := cmd.Start(); err != nil {
c1.Close()
c2.Close()
return nil, err
}
go func() {
cmd.Wait()
c2.Close()
}()
return c2
}))