table of contents
- unstable 0.13.1+ds1-2
DOCKER-BUILDX-RM(1) | DOCKER-BUILDX-RM(1) |
NAME¶
docker-buildx-rm - Remove one or more builder instances
SYNOPSIS¶
docker buildx rm [OPTIONS] [NAME] [NAME...]
DESCRIPTION¶
Removes the specified or current builder. It is a no-op attempting to remove the default builder.
OPTIONS¶
--all-inactive[=false] Remove all inactive builders
-f, --force[=false] Do not prompt for confirmation
-h, --help[=false] help for rm
--keep-daemon[=false] Keep the BuildKit daemon running
--keep-state[=false] Keep BuildKit state
OPTIONS INHERITED FROM PARENT COMMANDS¶
--builder="" Override the configured builder instance
EXAMPLE¶
### Remove all inactive builders (--all-inactive) {#all-inactive} Remove builders that are not in running state. ```console $ docker buildx rm --all-inactive WARNING! This will remove all builders that are not in running state. Are you sure you want to continue? [y/N] y
Override the configured builder instance (--builder) {#builder}¶
Same as ⟨/reference/cli/docker/buildx/#builder⟩.
Do not prompt for confirmation (--force) {#force}¶
Do not prompt for confirmation before removing inactive builders.
$ docker buildx rm --all-inactive --force
Keep the BuildKit daemon running (--keep-daemon) {#keep-daemon}¶
Keep the BuildKit daemon running after the buildx context is removed. This is useful when you manage BuildKit daemons and buildx contexts independently. Only supported by the
⟨/build/drivers/docker-container/⟩ and ⟨/build/drivers/kubernetes/⟩ drivers.
Keep BuildKit state (--keep-state) {#keep-state}¶
Keep BuildKit state, so it can be reused by a new builder with the same name. Currently, only supported by the ⟨/build/drivers/docker-container/⟩. ```
SEE ALSO¶
Feb 2025 |