DOCKER-BUILDX-INSPECT(1)

💖 docker-buildx-inspect — the manual, but make it cute 💖

okay bestie, so this is the manual page for docker-buildx-inspect, straight out of the Docker Buildx corner of the universe. It's a <pink>1</pink> page, it lives in section <pink>1</pink> of the manual, and it's about peeking at your builder. Let's get into it. ✨

---

🌸 NAME 🌸

docker-buildx-inspect — Inspect current builder instance

like, it looks at your builder. the current one. the whole vibe. 💅

---

🦋 SYNOPSIS 🦋

docker buildx inspect [NAME]

---

✨ DESCRIPTION ✨

Shows information about the current or specified builder.

that's it, that's the whole thing. it's giving "tell me everything about my builder" energy and honestly? obsessed. 🫶

---

🎀 OPTIONS 🎀

• --bootstrap[=false] — Ensure builder has booted before inspecting. yes queen, make sure it's awake before you go staring at it. 😌
• -h, --help[=false] — help for inspect. your lil rescue ladder when you forget how this works. 🪜

---

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

• --builder="" — Override the configured builder instance. you get to pick a different builder than the one configured, no cap.

---

🌈 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).

so basically: if your driver is docker-container, --bootstrap wakes up the BuildKit container and chills there until it's actually operational. and like, builds already bootstrap for you automatically, so this isn't strictly necessary — it's just a vibe check you can do on demand. same BuildKit container the whole time the builder node is alive, which you can see in buildx ls. 💖

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

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

same thing as buildx --builder, periodt.

💜 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:

default behavior = current builder. pass a name = that builder. iconic. and here's what it looks like when you inspect one 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.

$ 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

okay and also — the debug flag can be used to get more information about the builder, like so: $ docker --debug buildx inspect elated_tesla. more info, more lore. 🔥

---

⭐ SEE ALSO ⭐

• docker-buildx(1) — go read the parent page too, iykyk 💫

---

and that's the whole page bestie!! this one's from April 2025 (that's the date at the bottom, slay) — so go inspect something, you got this 💅✨🎀🦋