Jonathan A. Sternberg
7f5ff6b797
The package just causes the entire flow to be more complicated as build has to pretend it doesn't know about debug options and the debugger has to pretend it doesn't know about the build. This abstraction has been difficult when integrating a DAP command into this same workflow so I don't think this abstraction has much of a value. Signed-off-by: Jonathan A. Sternberg <jonathan.sternberg@docker.com>
25 lines
944 B
Markdown
25 lines
944 B
Markdown
# docker buildx debug
|
|
|
|
<!---MARKER_GEN_START-->
|
|
Start debugger (EXPERIMENTAL)
|
|
|
|
### Subcommands
|
|
|
|
| Name | Description |
|
|
|:---------------------------------|:--------------|
|
|
| [`build`](buildx_debug_build.md) | Start a build |
|
|
|
|
|
|
### Options
|
|
|
|
| Name | Type | Default | Description |
|
|
|:----------------|:---------|:--------|:-----------------------------------------------------------------|
|
|
| `--builder` | `string` | | Override the configured builder instance |
|
|
| `-D`, `--debug` | `bool` | | Enable debug logging |
|
|
| `--invoke` | `string` | | Launch a monitor with executing specified command (EXPERIMENTAL) |
|
|
| `--on` | `string` | `error` | When to launch the monitor ([always, error]) (EXPERIMENTAL) |
|
|
|
|
|
|
<!---MARKER_GEN_END-->
|
|
|