depot-container-builds

Name: depot-container-builds
Availability: InStock
Author: Agoric

Automate remote multi-platform container image builds with Depot.

357|255|Updated Nov 1, 2019

Search Tags:#multi-platform #docker #registry #ci-cd #remote-builds #depot #container-builds

Ready to run

npx skills add https://github.com/Agoric/agoric-sdk --skill depot-container-builds

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: depot-container-builds
Source: https://github.com/Agoric/agoric-sdk/tree/main/.agents/skills/depot-container-builds
Command: npx skills add https://github.com/Agoric/agoric-sdk --skill depot-container-builds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Depot Container Builds enables teams to run remote, high-performance Docker image builds and multi-platform images using Depot.

Core Features & Use Cases

Remote builds on ephemeral builders; images are cached remotely by default
Multi-platform builds using native CPUs for linux/amd64 and linux/arm64, with depot build and depot bake
Push, load, or save images to Depot Registry; supports secrets and SSH forwarding during builds
Use cases include CI/CD pipelines, debugging container builds, and migrating from docker build to Depot

Quick Start

Run a multi-platform remote build for your Docker image using Depot to generate and store the images in the remote cache.

Frequently Asked Questions about depot-container-builds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run multi-platform Docker builds for linux/amd64 and linux/arm64 in CI/CD?▼

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.

How do I migrate from docker build to remote container builds?▼

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.

Can I use secrets and SSH forwarding during remote container builds?▼

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.

What is the best way to cache Docker images across multiple CI/CD pipeline runs?▼

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.

Does Depot support pushing or loading images to a registry after building?▼

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.

What are the limitations of using ephemeral builders for container builds?▼

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.