# docker buildx create and use Command Reference

> Reference for docker buildx create and docker buildx use in CI: provision a builder instance with the docker-container driver for multi-arch and remote cache.

Source: https://latchkey.dev/learn/command-reference/docker-buildx-create-command-reference  
Updated: 2026-06-26

Create and select a BuildKit builder instance.

docker buildx create provisions a new builder. The default builder uses the limited docker driver; multi-arch builds and external cache backends require the docker-container driver, which create sets up. docker buildx use selects which builder subsequent build commands target.

## Common flags

- `--name` - name the builder instance
- `--driver` - builder driver, e.g. docker-container (needed for multi-arch and gha cache)
- `--use` - immediately switch to the new builder after creating it
- `--bootstrap` - start the builder right away instead of lazily on first build
- `--platform` - declare the platforms this builder supports

## Example

```shell
docker buildx create --name ci-builder --driver docker-container --use
docker buildx inspect --bootstrap
docker buildx use ci-builder
```

## In CI

Most workflows use the docker/setup-buildx-action which runs create/use for you, but doing it explicitly is useful in custom scripts. The docker-container driver is mandatory for --platform multi-arch and for type=gha cache; the default docker driver silently ignores those features.

## FAQ

### docker buildx create and use Command Reference?

docker buildx create provisions a new builder. The default builder uses the limited docker driver; multi-arch builds and external cache backends require the docker-container driver, which create sets up. docker buildx use selects which builder subsequent build commands target.

### In CI?

Most workflows use the docker/setup-buildx-action which runs create/use for you, but doing it explicitly is useful in custom scripts. The docker-container driver is mandatory for --platform multi-arch and for type=gha cache; the default docker driver silently ignores those features.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt