mirror of https://github.com/docker/docs.git
43 lines
2.0 KiB
Markdown
43 lines
2.0 KiB
Markdown
---
|
|
title: "Drivers overview"
|
|
keywords: build, buildx, driver, builder, docker-container, kubernetes, remote
|
|
redirect_from:
|
|
- /build/buildx/drivers/
|
|
- /build/building/drivers/
|
|
- /build/buildx/multiple-builders/
|
|
---
|
|
|
|
Buildx drivers are configurations for how and where the BuildKit backend runs.
|
|
Driver settings are customizable and allows fine-grained control of the builder.
|
|
Buildx supports the following drivers:
|
|
|
|
- `docker`: uses the BuildKit library bundled into the Docker daemon.
|
|
- `docker-container`: creates a dedicated BuildKit container using Docker.
|
|
- `kubernetes`: creates BuildKit pods in a Kubernetes cluster.
|
|
- `remote`: connects directly to a manually managed BuildKit daemon.
|
|
|
|
Different drivers support different use cases. The default `docker` driver
|
|
prioritizes simplicity and ease of use. It has limited support for advanced
|
|
features like caching and output formats, and isn't configurable. Other drivers
|
|
provide more flexibility and are better at handling advanced scenarios.
|
|
|
|
The following table outlines some differences between drivers.
|
|
|
|
| Feature | `docker` | `docker-container` | `kubernetes` | `remote` |
|
|
| :--------------------------- | :---------: | :----------------: | :----------: | :----------------: |
|
|
| **Automatically load image** | ✅ | | | |
|
|
| **Cache export** | Inline only | ✅ | ✅ | ✅ |
|
|
| **Tarball output** | | ✅ | ✅ | ✅ |
|
|
| **Multi-arch images** | | ✅ | ✅ | ✅ |
|
|
| **BuildKit configuration** | | ✅ | ✅ | Managed externally |
|
|
|
|
## What's next
|
|
|
|
Read about each of the Buildx drivers to learn about how they work and how to
|
|
use them:
|
|
|
|
- [Docker driver](./docker.md)
|
|
- [Docker container driver](./docker-container.md)
|
|
- [Kubernetes driver](./kubernetes.md)
|
|
- [Remote driver](./remote.md)
|