buildx/docs/reference/buildx_rm.md
Tonis Tiigi 7a7a9c8e01
commands: add debug as persistent flag
Allows using `--debug` to enable debug logging under
any subcommand. Currently it needed to be set as
`docker --debug buildx` meaning only way to enable debug
in standalone mode was to set env variable instead and
updating existing commands to add `--debug` was cumbersome.

Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
2024-08-16 13:20:28 +03:00

2.4 KiB

buildx rm

docker buildx rm [OPTIONS] [NAME] [NAME...]

Remove one or more builder instances

Options

Name Type Default Description
--all-inactive bool Remove all inactive builders
--builder string Override the configured builder instance
-D, --debug bool Enable debug logging
-f, --force bool Do not prompt for confirmation
--keep-daemon bool Keep the BuildKit daemon running
--keep-state bool Keep BuildKit state

Description

Removes the specified or current builder. It is a no-op attempting to remove the default builder.

Examples

Remove all inactive builders (--all-inactive)

Remove builders that are not in running state.

$ 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)

Same as buildx --builder.

Do not prompt for confirmation (--force)

Do not prompt for confirmation before removing inactive builders.

$ docker buildx rm --all-inactive --force

Keep the BuildKit daemon running (--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 docker-container and kubernetes drivers.

Keep BuildKit state (--keep-state)

Keep BuildKit state, so it can be reused by a new builder with the same name. Currently, only supported by the docker-container driver.