We're excited to introduce our third product, GitHub Actions Runners accelerated by Depot. All of the speed and performance from Depot-backed Docker image builds, now for your GitHub Actions jobs.
We are happy to reveal that Depot is now SOC 2 compliant. This is a significant milestone for us, so we thought we would share some more details and what it means for you.
We're excited to announce that we've now made Depot ephemeral registries available to depot bake commands so that you can save built images for multiple targets for later use in your CI workflows, to share with your team, or to push to remote registries.
This article walks you through how to use Depot's API within your own code to set up projects and run your Docker builds as a service on Depot's infrastructure.
We're excited to announce that we've released a set of Dagger Functions for Depot. You can use them to offload any build or bake operation to Depot and use the built image in your own Dagger code via our ephemeral registry.
Building multiple Docker images sequentially wastes time and duplicates work. `docker buildx bake` lets you define all your builds in one file and run them in parallel, with BuildKit automatically deduplicating shared dependencies.
Knowing how to optimize your Docker image builds to leverage the build cache as often as possible is critical to making your builds fast. We'll show you how the layer cache works and how to use the cache efficiently, so you can get the most out of your builds.
We're excited to release Depot ephemeral registries that allow you to save built images for later use in your CI workflows, to share with your team, or to push to remote registries.
