buildx/docs/reference/buildx_stop.md

# buildx stop

```
docker buildx stop [NAME]
```

<!---MARKER_GEN_START-->
Stop builder instance

### Options

| Name | Description |
| --- | --- |
| [`--builder string`](#builder) | Override the configured builder instance |


<!---MARKER_GEN_END-->

## Description

Stops the specified or current builder. This will not prevent buildx build to
restart the builder. The implementation of stop depends on the driver.

## Examples

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

Same as [`buildx --builder`](buildx.md#builder).
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 stop`

			```
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 stop [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			`Stop builder instance`

cli: fix builder persistent flag Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 3 years ago			`### Options`

			`\| Name \| Description \|`
			`\| --- \| --- \|`
			\| [`--builder string`](#builder) \| Override the configured builder instance \|

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`

			`Stops the specified or current builder. This will not prevent buildx build to`
			`restart the builder. The implementation of stop depends on the driver.`
cli: fix builder persistent flag Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> 3 years ago
			`## Examples`

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

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