# buildx rm
```
docker buildx rm [NAME]
```
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                      |
## 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.
```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)
Same as [`buildx --builder`](buildx.md#builder).
###  Do not prompt for confirmation (--force)
Do not prompt for confirmation before removing inactive builders.
```console
$ docker buildx rm --all-inactive --force
```
###  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).
###  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).