Man page - docker-buildx-inspect(1)

Packages contains this manual

Package:  docker-buildx
apt-get install docker-buildx

Manuals in package:
• 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)
Documentations in package:
• docker-buildx

Manual

DOCKER-BUILDX-INSPECT

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
OPTIONS INHERITED FROM PARENT COMMANDS
EXAMPLE
SEE ALSO

---

NAME

docker-buildx-inspect - Inspect current builder instance

SYNOPSIS

docker buildx inspect [NAME]

DESCRIPTION

Shows information about the current or specified builder.

OPTIONS

		--bootstrap [=false]	Ensure builder has booted before inspecting
		-h , --help [=false]	help for inspect

OPTIONS INHERITED FROM PARENT COMMANDS

--builder =""

Override the configured builder instance

EXAMPLE

### Ensure that the builder is running before inspecting (--bootstrap) {#bootstrap}

Use the ‘--bootstrap‘ option to ensure that the builder is running before
inspecting it. If the driver is ‘docker-container‘, then ‘--bootstrap‘ starts
the BuildKit container and waits until it’s operational. Bootstrapping is
automatically done during build, and therefore not necessary. The same BuildKit
container is used during the lifetime of the associated builder node (as
displayed in ‘buildx ls‘).

### Override the configured builder instance (--builder) {#builder}

Same as [‘buildx --builder‘](/reference/cli/docker/buildx/#builder).

### Get information about a builder instance

By default, ‘inspect‘ shows information about the current builder. Specify the
name of the builder to inspect to get information about that builder.
The following example shows information about a builder instance named
‘elated_tesla‘:

> **Note**
>
> The asterisk (‘*‘) next to node build platform(s) indicate they have been
> manually set during ‘buildx create‘. Otherwise the platforms were
> automatically detected.

‘‘‘console
$ docker buildx inspect elated_tesla
Name: elated_tesla
Driver: docker-container
Last Activity: 2022-11-30 12:42:47 +0100 CET

Nodes:
Name: elated_tesla0
Endpoint: unix:///var/run/docker.sock
Driver Options: env.BUILDKIT_STEP_LOG_MAX_SPEED="10485760" env.JAEGER_TRACE="localhost:6831" image="moby/buildkit:latest" network="host" env.BUILDKIT_STEP_LOG_MAX_SIZE="10485760"
Status: running
Flags: --debug --allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host
BuildKit: v0.10.6
Platforms: linux/arm64*, linux/arm/v7, linux/arm/v6
Labels:
org.mobyproject.buildkit.worker.executor: oci
org.mobyproject.buildkit.worker.hostname: docker-desktop
org.mobyproject.buildkit.worker.network: host
org.mobyproject.buildkit.worker.oci.process-mode: sandbox
org.mobyproject.buildkit.worker.selinux.enabled: false
org.mobyproject.buildkit.worker.snapshotter: overlayfs
GC Policy rule#0:
All: false
Filters: type==source.local,type==exec.cachemount,type==source.git.checkout
Keep Duration: 48h0m0s
Keep Bytes: 488.3MiB
GC Policy rule#1:
All: false
Keep Duration: 1440h0m0s
Keep Bytes: 24.21GiB
GC Policy rule#2:
All: false
Keep Bytes: 24.21GiB
GC Policy rule#3:
All: true
Keep Bytes: 24.21GiB

debug flag can also be used to get more information about the builder:

$ docker --debug buildx inspect elated_tesla

‘‘‘

SEE ALSO

docker-buildx(1)

---