new to Dagger - can't get a basic github action to work - all I get is error code 35. Help please! see my post here: https://discord.com/channels/707636530424
#Need help with github action error 35
solemn yacht
TOTALLY new to Dagger and working on wrapping my head around it. I have an issue I can't understand - re: github Actions and an error. Can anyone assist? Here's the github worfkflow yaml. on: workflow_dispatch
jobs:
hello_world_job:
runs-on: [ubuntu-latest]
steps:
name: dagger run
uses: dagger/dagger-for-github@v5
with:
workdir: db-service
verb: run
args: node build.js
cloud-token: ${{ secrets.DAGGER_CLOUD_TOKEN }}
version: "0.9.3"
name: dagger call
uses: dagger/dagger-for-github@v5
with:
module: github.com/shykes/daggerverse/hello
verb: call
args: with-greeting --greeting Hola with-name --name Jeremy message
cloud-token: ${{ secrets.DAGGER_CLOUD_TOKEN }}
delicate wolf
can you click the little arrow next to Run? there might be some more info hidden in that collapsed part
jagged bone
repro in progress as well
@solemn yacht this was showing two ways to run the action.
solemn yacht
jagged bone
One for the previous "SDK program" style of Dagger that you'd run with go, node, or python and one for the current style using Dagger Functions in Modules.
Which kind do you want to use?
Also, I get that you're brand new to Dagger 🙂
I'd suggest that you use Functions as currently shown in the docs.
solemn yacht
<@283963906299265024> this was showing two ways to run the action.
Thanks and I agree - but what I don't understand is this is a very simple workflow but I can't get it to run and the error code I can't find anything on. I know I'm TOTALLY new to Dagger as of last night - and wanted to just run a hello world container via a pipeline to get a handle on this thing works, but any example of a github action I've yet to get to run. So I'm missing something obviously. I'm SUPER interested in getting this running so I can see how to use it, but I need a working container example first
jagged bone
Often we suggest running locally first. Is that an option?
Do you have docker/podman locally?
solemn yacht
One for the previous "SDK program" style of Dagger that you'd run with `go`, `no...
I do and can - I got that working without much issue last night. I was able to run the cli and boom - hello world - but I can't seem to get a github action workflow to run. ex: https://github.com/dagger/dagger-for-github - the dagger call fails the same - error code 35. I was hoping to see hola jeremy but just got error code 35 when I tried the yaml from the gha repo
jagged bone
So you'd just install dagger and run
dagger -m github.com/shykes/daggerverse/hello call hello --greeting Hola --name Jeremy
to get the equiv of the GitHub Action example from the README
Ah, cool. Let me repro that part. One sec.
jagged bone
In GitHub UI, Actions tab, I created a new workflow using
https://github.com/<my org>/<my repo>/actions/new
solemn yacht
following so far.. 🙂
jagged bone
Then I deleted the existing actions and added the code example
Here is result of run after I committed it.
https://github.com/jpadams/test-action/actions/runs/9033948910/job/24825381722#step:2:304
solemn yacht
now we're talking - this is EXACTLY what I was after - I personally learn more by doing than documentation and get a sense of it and then drill down into the weeds as necessary, so this should put me on a track. THANKS a million for taking the time to help out a new user. I'm VERY VERY interested in this as I like the idea of not commiting 1000x to a repo just because of syntax or a bad line of code etc. Super excited to dive in!
jagged bone
now we're talking - this is EXACTLY what I was after - I personally learn more b...
Welcome to the community! Thanks for your question, it makes it better for everyone 🙂
solemn yacht
Thank you for the warm welcome! I'm running the code in a min - let you know how it goes.
one other quick question - why the need for the cloud id?
jagged bone
Oh! Hah! yeah, that's not needed at all, but, if you have a Dagger Cloud account, you can see the run there.
solemn yacht
That helps , thank you! Now as to the code - same error. I'm SO puzzled.
ignore the commented out step. Here's my yaml.
jagged bone
Is it in a public repo? can you point me to it?
solemn yacht
it is not public unfortunately....it's my work org.
running on github hosted runner - ubuntu latest
I take that back - running on self hosted runner.
the runner is running ubuntu 2204
jagged bone
Got it. Do you know if you're running on GitHub Enterprise? Like self-hosted GHES?
solemn yacht
we run github enterprise (I thiunk...I'm not in charge of GH so not 100% on that) - but we have self hosted runners hosted internally exposed to github by way of delegating hosted nics from our internal network to github so the runners they build use our nics and we can have internal access.
jagged bone
Hmmm...yeah, I should fire up GitHub Enterprise Server and see how compatible the GitHub Actions support is vs cloud-based GH Enterprise Cloud, github.com...
solemn yacht
now our github runners do have whitelisted internet access. AKA - your cloud access may not be allowed. For example: If I want to access the atlassian jira api from a github runner, I have to write some terraform to add a firewall rule to allow access to that from our github runner subnet. Now if the cloud part is not neeed but throwing this off, we coudl drop the cloud part - idk, just spitballing.
also - we don't host GHE, we use GHE from the cloud entirely if that helps re: your previous comment
so yes, our GHE should be cloud.
jagged bone
I wonder if we can get some more debug logging going. We could add to the args:... one sec.
Also here's what the cloud output looks like for the simple run. Much more useful in complex pipelines 🙂
solemn yacht
oh nice - I had yet to see what the cloud stuff looked like - thanks for the that!
I can add more logging - let me know what to add/change and will do.
jagged bone
just adding -d should do it
-d, --debug show debug logs and full verbosity
I'd add to to the beginning of the args:
solemn yacht
roger- like this?
jagged bone
yep!
solemn yacht
commiting - brb
jagged bone
Just updated mine 🤞
https://github.com/jpadams/test-action/blob/main/.github/workflows/blank.yml#L30
solemn yacht
boo hiss
I wonder if it is just my work's runners - let me try something quickly....brb
jagged bone
solemn yacht
it''s something to do with our self hosted runners. I have night job where it's much more relaxed re: networking etc - and we use the gh hosted runners - ran perfectly.
I'd take a bet that the runners we have do NOT allow access to dagger.io to install/dl dagger stuff -
ok - that clears up my sanity check - makes sense. I TRULY appreciate you working with me on this - its that second set of eyes that I needed to make sure the github workflow was not wrong....so that was very helpful.
@jagged bone - I can't thank you enough for the help this morning!
lone cipher
I'd take a bet that the runners we have do NOT allow access to dagger.io to inst...
If GitHub and docker hub is allowed in your runners you can get past this by downloading the CLI from our GitHub releases and putting it in your path. That's pretty much what our install script does.
