buildx/docs/reference/buildx_rm.md

# buildx rm

```
docker buildx rm [NAME]
```

<!---MARKER_GEN_START-->
Remove a builder instance

### Options

| Name                                | Type     | Default | Description                              |
|:------------------------------------|:---------|:--------|:-----------------------------------------|
| [`--all-inactive`](#all-inactive)   |          |         | Remove all inactive builders             |
| [`--builder`](#builder)             | `string` |         | Override the configured builder instance |
| [`-f`](#force), [`--force`](#force) |          |         | Do not prompt for confirmation           |
| [`--keep-daemon`](#keep-daemon)     |          |         | Keep the buildkitd daemon running        |
| [`--keep-state`](#keep-state)       |          |         | Keep BuildKit state                      |


<!---MARKER_GEN_END-->

## Description

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

## Examples

### <a name="all-inactive"></a> Remove all inactive builders (--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
```

### <a name="builder"></a> Override the configured builder instance (--builder)

Same as [`buildx --builder`](buildx.md#builder).

### <a name="force"></a> Do not prompt for confirmation (--force)

Do not prompt for confirmation before removing inactive builders.

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

### <a name="keep-daemon"></a> Keep the buildkitd daemon running (--keep-daemon)

Keep the buildkitd daemon running after the buildx context is removed. This is useful when you manage buildkitd daemons and buildx contexts independently.
Currently, only supported by the [`docker-container` and `kubernetes` drivers](buildx_create.md#driver).

### <a name="keep-state"></a> 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](buildx_create.md#driver).
docs: standardize format for usage Use the usage output of `--help` for each subcommand, to make sure all flags/options are included on the page, and to make it easier to keep docs in sync. Note that the usage output is only used when reading these docs on GitHub; docs.docker.com only consumes the "description" and "example" sections (when present), and generates flag information and usage output from source Signed-off-by: Sebastiaan van Stijn <github@gone.nl> 4 years ago			`# buildx rm`

			```
docs: reference docs updates Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl> 4 years ago			`docker buildx rm [NAME]`
			```
docs: standardize format for usage Use the usage output of `--help` for each subcommand, to make sure all flags/options are included on the page, and to make it easier to keep docs in sync. Note that the usage output is only used when reading these docs on GitHub; docs.docker.com only consumes the "description" and "example" sections (when present), and generates flag information and usage output from source Signed-off-by: Sebastiaan van Stijn <github@gone.nl> 4 years ago
docs: reference docs updates Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl> 4 years ago			`<!---MARKER_GEN_START-->`
docs: standardize format for usage Use the usage output of `--help` for each subcommand, to make sure all flags/options are included on the page, and to make it easier to keep docs in sync. Note that the usage output is only used when reading these docs on GitHub; docs.docker.com only consumes the "description" and "example" sections (when present), and generates flag information and usage output from source Signed-off-by: Sebastiaan van Stijn <github@gone.nl> 4 years ago			`Remove a builder instance`

Keep BuildKit state in a volume Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 4 years ago			`### Options`

go.mod: update cli-docs-tool v0.5.1 and re-generate docs Signed-off-by: Sebastiaan van Stijn <github@gone.nl> 2 years ago			`\| Name \| Type \| Default \| Description \|`
			`\|:------------------------------------\|:---------\|:--------\|:-----------------------------------------\|`
			\| [`--all-inactive`](#all-inactive) \| \| \| Remove all inactive builders \|
			\| [`--builder`](#builder) \| `string` \| \| Override the configured builder instance \|
			\| [`-f`](#force), [`--force`](#force) \| \| \| Do not prompt for confirmation \|
			\| [`--keep-daemon`](#keep-daemon) \| \| \| Keep the buildkitd daemon running \|
			\| [`--keep-state`](#keep-state) \| \| \| Keep BuildKit state \|
Keep BuildKit state in a volume Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 4 years ago
docs: reference docs updates Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl> 4 years ago
			`<!---MARKER_GEN_END-->`
docs: split reference docs to separate files Signed-off-by: Sebastiaan van Stijn <github@gone.nl> 4 years ago
			`## Description`

			`Removes the specified or current builder. It is a no-op attempting to remove the`
			`default builder.`
Keep BuildKit state in a volume Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 4 years ago
			`## Examples`

cli: add --all-inactive and --force flags for rm command Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 3 years ago			`### <a name="all-inactive"></a> Remove all inactive builders (--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`
			```

cli: fix builder persistent flag Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 3 years ago			`### <a name="builder"></a> Override the configured builder instance (--builder)`

			Same as [`buildx --builder`](buildx.md#builder).

cli: add --all-inactive and --force flags for rm command Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 3 years ago			`### <a name="force"></a> Do not prompt for confirmation (--force)`
Keep BuildKit state in a volume Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 4 years ago
cli: add --all-inactive and --force flags for rm command Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 3 years ago			`Do not prompt for confirmation before removing inactive builders.`

			```console
			`$ docker buildx rm --all-inactive --force`
			```
Add an option to buildx rm to keep the buildkitd daemon running Add --keep-daemon to the `rm` command option to preserve the buildkitd daemon after the buildx context is deleted. Signed-off-by: Mayeul Blanzat <mayeul.blanzat@datadoghq.com> 3 years ago
			`### <a name="keep-daemon"></a> Keep the buildkitd daemon running (--keep-daemon)`

			`Keep the buildkitd daemon running after the buildx context is removed. This is useful when you manage buildkitd daemons and buildx contexts independently.`
			Currently, only supported by the [`docker-container` and `kubernetes` drivers](buildx_create.md#driver).
cli: add --all-inactive and --force flags for rm command Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 3 years ago
			`### <a name="keep-state"></a> 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](buildx_create.md#driver).