-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Self hosted runners - ARC #106
Comments
Just checked this and it happens because |
this seemed to work, it's the In any case we should handle this gracefully also. |
Yes!! This is a big part of the solution. Here is some yaml to get Summerwind’s ubuntu 22.04 runner:
True, we never get to run a pipeline. The issue is, that the Summerwind image user that runs everything,
What you can also do, is run a custom version of the Summerwind docker image. Here I change the owernship of the folder /usr/local/bin to runner, and now it all works!
|
This PR #105 fixes the /use/local path issue. This problem will be resolved in the next release |
@alex9fredericks Please confirm that you're good to go with the |
Hey @jpadams, everything worked fine at the first run! :) This test was done with a simplified runner image:
|
What is the issue?
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.
Dagger version
dagger v0.9.3
Steps to reproduce
Problem and Solution (1)
The following script works fine with GitHub runners but not with ARC:
Solution
This is my workaround for the moment!! 😄 :
Another varation that still does not work (2)
I also tried another variation, based on a suggestion from @marcosnils!
This still produces another error:
Log output
No response
The text was updated successfully, but these errors were encountered: