I have a GitHub action that calls dagger/dagger-for-github@v6 on a self-hosted runner. I'm running Dagger commands locally on the same machine registered as the self-hosted runner in GitHub Actions to test my pipeline for different projects. However, when I run these commands locally, my pipeline gets stuck and takes significantly longer to complete.
#Can dagger engine handle multiple request at a time?
sweet igloo
cedar ivy
Yes, Dagger can handle multiple requests at the time in parallel without issues
sweet igloo
Yes, Dagger can handle multiple requests at the time in parallel without issues
but its pausing/slowing down my dagger command while ci/cd pipeline is runnin on same mac machine with github self hosted runner with same engine, any solution?
cedar ivy
but its pausing/slowing down my dagger command while ci/cd pipeline is runnin on...
I'd assume you're running this in Docker?
keep into account that the Docker VM generally doesn't have that many resources in a Mac. I'd assume this is a resource consumption issue, not something related to Dagger
sweet igloo
should we run dagger by installing locally in machine?
i think dagger cli by default get new dagger container to run pipelines, so it's right way ot not?
cedar ivy
have you tried adding more resources to the Docker VM?