docker / buildx

Buildx Drivers

Buildx Drivers Overview

Buildx provides various drivers to execute builds in different environments. Each driver offers distinct capabilities and configurations. This section outlines the available drivers, their functionalities, and configuration options.

Default Driver: docker

The docker driver is the default driver for Buildx and is used for local build execution. It leverages Docker’s native build capabilities.

Example:

buildx build --driver docker --platform linux/amd64 .

docker-container Driver

The docker-container driver enables building images within a Docker container. This driver is ideal for environments where direct access to the host system is restricted or for building images with specific runtime dependencies.

Configuration Options:

  • container: Specifies the Docker container image to use for the build.
  • context: Specifies the context path to be mounted within the container.
  • network: Defines the network mode for the build container.
  • privileged: Enables privileged mode for the container, granting access to host devices.

Example:

buildx build --driver docker-container --container ubuntu:latest --platform linux/amd64 .

kubernetes Driver

The kubernetes driver allows building images within a Kubernetes cluster. It offers scalability and resource management capabilities, making it suitable for large-scale builds.

Configuration Options:

  • context: Specifies the context path to be mounted within the Kubernetes pod.
  • namespace: Defines the Kubernetes namespace for the build pod.
  • image: Specifies the container image to use for the build.
  • resources: Configures resource limits and requests for the build pod.
  • serviceAccount: Specifies the Kubernetes service account to use for the build pod.

Example:

buildx build --driver kubernetes --context . --namespace default --image ubuntu:latest --platform linux/amd64 .

remote Driver

The remote driver allows building images on remote nodes, enabling distributed builds. It leverages Docker’s remote build capabilities and requires a remote Docker daemon configured for access.

Configuration Options:

  • remote: Specifies the URL of the remote Docker daemon.
  • context: Defines the path to the build context on the remote node.
  • dockerfile: Specifies the Dockerfile path on the remote node.

Example:

buildx build --driver remote --remote tcp://remote-docker-host:2375 --context /path/to/context --platform linux/amd64 .

Choosing a Driver

The selection of an appropriate Buildx driver depends on the specific build requirements and the available resources.

  • For local builds, the docker driver is the default and recommended choice.
  • For isolated build environments or specific runtime dependencies, consider the docker-container driver.
  • For large-scale builds and resource management, the kubernetes driver provides scalability and flexibility.
  • For distributed builds, utilize the remote driver to leverage remote Docker daemons.