depot-container-builds

Multi-platform Docker builds for linux/amd64 and linux/arm64 run remotely on ephemeral Depot builders using native CPUs. This approach automates consistent image creation and caching across architectures, supporting both depot build and depot bake workflows for CI/CD integration.

Migrating from docker build to remote container builds uses Depot to execute high-performance Docker image builds on ephemeral remote builders. Images are cached remotely by default, providing scalable and consistent artifact creation without local Docker overhead.

Remote container builds support secrets and SSH forwarding during the build process. This allows secure access to private repositories and sensitive credentials directly within the Depot build and depot bake workflows without exposing them in the final image.

Caching Docker images across pipeline runs is handled automatically by storing images in a remote cache on ephemeral Depot builders. This ensures fast subsequent builds by retrieving cached layers directly from the Depot Registry.

Depot supports pushing, loading, or saving images to the Depot Registry after building. This provides flexible artifact management and distribution options for multi-platform images generated through the remote build process.

Ephemeral builders provide isolated, remote execution for container builds but do not retain state between runs. While remote caching mitigates rebuild times, local Docker daemon loading may be slower for very large multi-platform images compared to native local builds.