Skip to main content

Integrate Dagger with GitHub Actions


This documentation is for an older version of Dagger, which is no longer actively maintained.

We encourage you to upgrade and refer to the documentation for the most current version.

If you cannot upgrade to the latest version, please contact us in the help forum on Discord. When contacting us, please let us know why you cannot move to the latest version. From there, our team will work with you on your use case.

This tutorial illustrates how to use GitHub Actions and Dagger to build, push and deploy Docker images to Cloud Run.


We assume that you've finished our 106-cloudrun tutorial as this one continues right after.

Setup new GitHub repo

Push existing examples/todoapp directory to your new GitHub repo (public or private). It should contain all the code from, gcpcloudrun and .dagger/env/gcpcloudrun/ directory.

Add GitHub Actions Secret

Dagger encrypts all input secrets using your key stored at ~/.config/dagger/keys.txt. Copy the entire line starting with AGE-SECRET-KEY- and save it to a GitHub secret named DAGGER_AGE_KEY. In case you don't know how to create secrets on GitHub take a look at this tutorial.

Create a GitHub Actions Workflow

Create .github/workflows/gcpcloudrun.yml file and paste the following code into it:

name: CloudRun

- main

runs-on: ubuntu-latest
- name: Checkout code
uses: actions/checkout@v2
- name: Dagger
uses: dagger/dagger-for-github@v3
age-key: ${{ secrets.DAGGER_AGE_KEY }}
args: up -e gcpcloudrun


On any push to main branch this workflow should run and deploy the todoapp to your GCP Cloud Run instance.