You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
44 lines
1.0 KiB
Markdown
44 lines
1.0 KiB
Markdown
# buildx inspect
|
|
|
|
```
|
|
Usage: docker buildx inspect [NAME]
|
|
|
|
Inspect current builder instance
|
|
|
|
Options:
|
|
--bootstrap Ensure builder has booted before inspecting
|
|
--builder string Override the configured builder instance
|
|
```
|
|
|
|
## Description
|
|
|
|
Shows information about the current or specified builder.
|
|
|
|
Example:
|
|
|
|
```console
|
|
$ docker buildx inspect elated_tesla
|
|
|
|
Name: elated_tesla
|
|
Driver: docker-container
|
|
|
|
Nodes:
|
|
Name: elated_tesla0
|
|
Endpoint: unix:///var/run/docker.sock
|
|
Status: running
|
|
Platforms: linux/amd64
|
|
|
|
Name: elated_tesla1
|
|
Endpoint: ssh://ubuntu@1.2.3.4
|
|
Status: running
|
|
Platforms: linux/arm64, linux/arm/v7, linux/arm/v6
|
|
```
|
|
|
|
### `--bootstrap`
|
|
|
|
Ensures that the builder is running before inspecting it. If the driver is
|
|
`docker-container`, then `--bootstrap` starts the buildkit container and waits
|
|
until it is operational. Bootstrapping is automatically done during build, it is
|
|
thus not necessary. The same BuildKit container is used during the lifetime of
|
|
the associated builder node (as displayed in `buildx ls`).
|