Kyle Galbraith

See how much of your builds are cached and how much time that saves you and your team. In addition, monitor how much provisioned cache you are using for each build architecture.

Fast image builds just got even faster with the introduction of bigger builder machines that have 4x the compute power.

With CLI version 1.5.0, buildx bake comes to Depot via the depot bake command. Build multiple Docker images concurrently from an HCL, JSON, or Docker Compose file.

BuildKit cache mounts provide a more fine-grained cache that allows you to leverage pre-computed work even when the Docker layer cache invalidates.

Building your Docker images just got even faster with the ability to launch Depot builders in the region closest to your registries.

The easiest way to get faster Docker image builds inside of Google Cloud Build is to make use of the layer cache as frequently as possible. But options available today in Cloud Build can often negate the advantages of layer caching.

If you use the asdf version manager, you can now add our Depot CLI as a plugin to manage all of your versions in one place.

We made it even easier to sign up and try out Depot by adding support for logging in with Google and Microsoft accounts.

Self-hosted Depot builders are here! Launch builders in your own AWS accounts on a per-project basis and connect directly to them without passing through any Depot proxy.

Reducing the overall image size is key to building and launching Docker images as quickly as possible. The smaller the image size, the less network bandwidth we have to consume to build and launch it.

You can now authenticate to Depot with a project-specific API token, for fine-grained access control over your Docker builds.

Building Arm and multi-architecture containers today is challenging. In this post, we explore the current options and how Depot addresses each challenge.