Dagger for GitHub - Self Hosted Runners - ARC

[magic geode]

The issue I'd like to log, just more FYI, is that it seems that you cannot run the GitHub Dagger action, out of the box, with self hosted runners, on Kubernetes. I installed the ARC for GitHub, with Helm, with the quick-start guide. (With Helm, this was actually quite easy to install). I managed to register some runners, and most of the workflows just run fine. For reference, workflows that used the "docker/build-push-action@v4.1.0", did work right away.

The following script works fine with GitHub runners but not with ARC:

name: 40_dagger_demo.yaml
permissions:
  contents: read
  packages: write
on:
  push:
    branches:
      - main
    paths:
      - 'apps/demo/**’
      - '.github/workflows/dagger_demo.yaml'
concurrency:
  group: ${{ github.ref }}-${{ github.workflow }}
  cancel-in-progress: true
jobs:
  build:
    name: build
    # runs-on: ubuntu-latest
    runs-on: self-hosted
    steps:
      - uses: actions/checkout@v3
      - name: '+ Install dagger-io'
        run: pip install dagger-io
      - name: '+ Run Dagger pipeline'
        uses: dagger/dagger-for-github@v5
        with:
          workdir: apps/demo
          verb: run
          args: python main.py "${{ secrets.DAGGER_KEY }}" github_username
          version: "0.9.3"

This is my workaround for the moment!! 😄 :

    steps:
      - name: '+ Setup python'
        uses: actions/setup-python@v5
        with:
          python-version: 'pypy3.10'
      - name: '+ Check out the repo'
        uses: actions/checkout@v4
      - name: '+ Install manual'
        run: pip install anyio dagger-io==0.9.3
      - name: '+ Run Dagger Pipeline'
        run: cd $GITHUB_WORKSPACE/apps/demo/ && python main.py "${{ secrets.DAGGER_KEY }}" github_username

[tidal kraken]

thx for reporting this. I can take a look tomorrow 🙏

would you please open an issue in the dagger/dagger repo if possible?

[tidal kraken]

I see that in this steps you're doing some things like you didn't do in the previous one like calling setup-python and checkout@v4. Have you tried if the action works with these steps being called before?

the error that you get in the when using the action doesn't seem to be coming from the dagger action itself but from the pip install step which is unrelated to the Dagger action

[magic geode]

Hey, to properly answer you. Yes indeed, I tried this varation as well. This actually generates the most interesting error.

ps: just created an issue on GitHub *

name: 40_dagger_demo.yaml
permissions:
  contents: read
  packages: write
on:
  push:
    branches:
      - main
    paths:
      - 'apps/demo/**'
      - '.github/workflows/40_dagger_demo.yaml'
concurrency:
  group: ${{ github.ref }}-${{ github.workflow }}
  cancel-in-progress: true
jobs:
  build:
    name: build
    # ---
    # runs-on: ubuntu-latest
    # ---
    runs-on: self-hosted
    steps:
      - name: '+ Setup python'
        uses: actions/setup-python@v5
        with:
          python-version: 'pypy3.10'
      - name: '+ Check out the repo'
        uses: actions/checkout@v4
      - name: '+ Run Dagger pipeline'
        uses: dagger/dagger-for-github@v5
        with:
          workdir: apps/demo
          verb: run
          args: python main.py "${{ secrets.DAGGER_KEY }}" github_username
          version: "0.9.3"

[stark bone]

@magic geode if possible, could you use this version of the dagger-for-github action to see if it fixes one or more of your errors?

https://github.com/egladman/dagger-for-github/tree/main

I'm looking to accept this PR, but I'm curious in your case if it moves things int the right direction.

[tidal kraken]

found the issue and sent a PR in our repo Jeremy

added a comment to the original issue with the reason

[magic geode]

Wow!! This is so cool. Thank you!! (I’m in the middle of porting my pipelines. I’m moving it all to Dagger now 😄 )

[magic geode]

Hey! you were right, that was the way!! - i'm super stoked about this all. Dagger is really fantastic!