Platform

Resources

Community

Platform

Resources

Community

Dagger ❤️ Depot

January 15, 2025

Jan 15, 2025

Share
Share
Share
Share

Today we’re thrilled to announce a new way to integrate Dagger and GitHub Actions, with the help of our newest partner: Depot.

This announcement kicks off our new “Dagger Powered” program - an initiative to partner directly with your favorite infrastructure providers, and make sure Dagger takes full advantage of each platform’s unique capabilities. In the case of Depot, that means managed GitHub Actions runners with distributed caching out of the box - something many Dagger users have been asking for!

Depot: Our First Partner

Running Dagger on GitHub Actions is easy: just add a few lines of configuration, and you’re done. However running Dagger at optimal performance on GitHub Actions is not so easy: GitHub stock runners don’t persist the Dagger cache, so your options are either a) run Dagger on an empty cache, or b) host your own runners, typically using Kubernetes and your storage technology of choice.

For those who want to fully leverage Dagger’s cache without having to self-host their CI, there was no good option - until today.

We’re excited to introduce Depot as the first partner in the Dagger Powered program. The combination of Dagger and Depot’s GitHub Actions runners makes it easier than ever to integrate Dagger into your workflows without sacrificing performance.

Why Use Dagger with Depot Runners?

  • Simple Setup: Get started with just a single line change in your GitHub Actions configuration. Update the runs-on: line, and you’re ready to go.

    • runs-on: depot-ubuntu-22.04-4,dagger=0.15.2

  • Pre-installed Dagger: Everything you need is pre-installed, ready to call your pipeline’s functions.

    • run: dagger call build

  • Caching That Just Works: Efficient caching ensures faster builds with zero configuration.

What’s Next?

This is just the beginning. With the Dagger Powered program, we’re building a set of compute and storage integrations across a range of platforms to meet developers where they are. Keep an eye out for more announcements as we expand to other platforms and partners.

Ready to Try It Out?

Head to our documentation to learn more about using Dagger with Depot GitHub Actions runners, or check out the video below to see how quickly you can get started.


Today we’re thrilled to announce a new way to integrate Dagger and GitHub Actions, with the help of our newest partner: Depot.

This announcement kicks off our new “Dagger Powered” program - an initiative to partner directly with your favorite infrastructure providers, and make sure Dagger takes full advantage of each platform’s unique capabilities. In the case of Depot, that means managed GitHub Actions runners with distributed caching out of the box - something many Dagger users have been asking for!

Depot: Our First Partner

Running Dagger on GitHub Actions is easy: just add a few lines of configuration, and you’re done. However running Dagger at optimal performance on GitHub Actions is not so easy: GitHub stock runners don’t persist the Dagger cache, so your options are either a) run Dagger on an empty cache, or b) host your own runners, typically using Kubernetes and your storage technology of choice.

For those who want to fully leverage Dagger’s cache without having to self-host their CI, there was no good option - until today.

We’re excited to introduce Depot as the first partner in the Dagger Powered program. The combination of Dagger and Depot’s GitHub Actions runners makes it easier than ever to integrate Dagger into your workflows without sacrificing performance.

Why Use Dagger with Depot Runners?

  • Simple Setup: Get started with just a single line change in your GitHub Actions configuration. Update the runs-on: line, and you’re ready to go.

    • runs-on: depot-ubuntu-22.04-4,dagger=0.15.2

  • Pre-installed Dagger: Everything you need is pre-installed, ready to call your pipeline’s functions.

    • run: dagger call build

  • Caching That Just Works: Efficient caching ensures faster builds with zero configuration.

What’s Next?

This is just the beginning. With the Dagger Powered program, we’re building a set of compute and storage integrations across a range of platforms to meet developers where they are. Keep an eye out for more announcements as we expand to other platforms and partners.

Ready to Try It Out?

Head to our documentation to learn more about using Dagger with Depot GitHub Actions runners, or check out the video below to see how quickly you can get started.


Today we’re thrilled to announce a new way to integrate Dagger and GitHub Actions, with the help of our newest partner: Depot.

This announcement kicks off our new “Dagger Powered” program - an initiative to partner directly with your favorite infrastructure providers, and make sure Dagger takes full advantage of each platform’s unique capabilities. In the case of Depot, that means managed GitHub Actions runners with distributed caching out of the box - something many Dagger users have been asking for!

Depot: Our First Partner

Running Dagger on GitHub Actions is easy: just add a few lines of configuration, and you’re done. However running Dagger at optimal performance on GitHub Actions is not so easy: GitHub stock runners don’t persist the Dagger cache, so your options are either a) run Dagger on an empty cache, or b) host your own runners, typically using Kubernetes and your storage technology of choice.

For those who want to fully leverage Dagger’s cache without having to self-host their CI, there was no good option - until today.

We’re excited to introduce Depot as the first partner in the Dagger Powered program. The combination of Dagger and Depot’s GitHub Actions runners makes it easier than ever to integrate Dagger into your workflows without sacrificing performance.

Why Use Dagger with Depot Runners?

  • Simple Setup: Get started with just a single line change in your GitHub Actions configuration. Update the runs-on: line, and you’re ready to go.

    • runs-on: depot-ubuntu-22.04-4,dagger=0.15.2

  • Pre-installed Dagger: Everything you need is pre-installed, ready to call your pipeline’s functions.

    • run: dagger call build

  • Caching That Just Works: Efficient caching ensures faster builds with zero configuration.

What’s Next?

This is just the beginning. With the Dagger Powered program, we’re building a set of compute and storage integrations across a range of platforms to meet developers where they are. Keep an eye out for more announcements as we expand to other platforms and partners.

Ready to Try It Out?

Head to our documentation to learn more about using Dagger with Depot GitHub Actions runners, or check out the video below to see how quickly you can get started.


Get Involved With the community

Discover what our community is doing, and join the conversation on Discord & GitHub to help shape the evolution of Dagger.

Subscribe to our newsletter

Get Involved With the community

Discover what our community is doing, and join the conversation on Discord & GitHub to help shape the evolution of Dagger.

Subscribe to our newsletter

Get Involved With the community

Discover what our community is doing, and join the conversation on Discord & GitHub to help shape the evolution of Dagger.

Subscribe to our newsletter