Man page - docker-buildx-dial-stdio(1)
Packages contains this manual
- docker-buildx-inspect(1)
- docker-buildx-rm(1)
- docker-buildx-ls(1)
- docker-buildx-bake(1)
- docker-buildx-imagetools-inspect(1)
- docker-buildx-build(1)
- docker-buildx-version(1)
- docker-buildx-imagetools(1)
- docker-buildx-create(1)
- docker-buildx-use(1)
- docker-buildx-dial-stdio(1)
- docker-buildx(1)
- docker-buildx-imagetools-create(1)
- docker-buildx-stop(1)
- docker-buildx-prune(1)
- docker-buildx-uninstall(1)
- docker-buildx-du(1)
- docker-buildx-install(1)
apt-get install docker-buildx
Manual
DOCKER-BUILDX-DIAL-STDIO
NAMESYNOPSIS
DESCRIPTION
OPTIONS
OPTIONS INHERITED FROM PARENT COMMANDS
EXAMPLE
SEE ALSO
NAME
docker-buildx-dial-stdio - Proxy current stdio streams to builder instance
SYNOPSIS
docker buildx dial-stdio
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.
OPTIONS
|
-h , --help [=false] |
help for dial-stdio |
||
|
--platform ="" |
Target platform: this is used for node selection |
||
|
--progress ="quiet" |
Set type of progress output (auto, plain, tty). |
OPTIONS INHERITED FROM PARENT COMMANDS
|
--builder ="" |
Override the configured builder instance |
EXAMPLE
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.
‘‘‘go
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
}))
‘‘‘
SEE ALSO
docker-buildx(1)