Skip to content
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

Can I use this as a replacement for the official github action runner, too? #475

Open
cleeland opened this issue Dec 12, 2024 · 8 comments

Comments

@cleeland
Copy link

I would like to use github actions on windows with containers specified in the workflows, and it appears that this fork has that capability. Can I use this as a direct replacement for the official github-released actions runner, possibly as simply as unzip'ing this release into the same folder?

Also, what is the difference between the "fxindependent" releases and the non-fxindependent?

@ChristopherHX
Copy link
Owner

Also, what is the difference between the "fxindependent" releases and the non-fxindependent?

fxdependent means, bring your own dotnet runtime. Currently one of

  • .net6
  • .net8 (forward compat)

E.g. dotnet Runner.Listener.dll would be called internally, the available dotnet tool can be compiled once and installed on win/linux/mac and intel or arm via this packaging.

The non fxdependent releases match the actions/runner bin folder.

Can I use this as a direct replacement for the official github-released actions runner, possibly as simply as unzip'ing this release into the same folder?

It has been some time between me connecting this runner to github.com and now. It has been possible, but I or you would need to check it.

Here an instruction

@cleeland
Copy link
Author

Thanks for the info! I'll will check it.

What is the latest official action runner version on which this is based?

@cleeland
Copy link
Author

What is the latest official action runner version on which this is based?

Treating the official as upstream, it looks like maybe it's 2.316? If so, I might have to either try to merge myself with 2.319 or later, or wait for you to re-sync if it gets beyond my capabilities. I need some stuff from 319 and beyond to work with some required actions.

I guess I could also explore porting your container changes back over to 2.321 (latest official at time of this writing), but I expect that might actually be more difficult/error-prone.

@ChristopherHX
Copy link
Owner

What is the latest official action runner version on which this is based?

As of my 3.12.0 release: based on v2.319.1 ~ snapshot end of August.

Since I use 3.x.x runner releases, you don't need disableupdate and the 30 days deprecation logic is skipped as well.

My github-act-runner written from scratch had no breakings between August and December, so I assume this one has no problems until somewhere in January as well.

@cleeland
Copy link
Author

Oh, excellent! Life just got potentially simpler. Will report back soon.

@cleeland
Copy link
Author

Took me a little longer than I'd hoped, but it appears to work.

@ChristopherHX
Copy link
Owner

Good to know that this works for you.
Did you face any obstacles during your setup?
I could publish the original runner packages again (currently available as actions artifact from ci).
In the meantime I merged the latest actions/runner from today into this fork, so 3.13 can make use of this runner version as soon as I create the next release.

@cleeland
Copy link
Author

No technical issues that weren't my own fault. I think maybe I had to remove the runner registration, then add it again? It's probably significant that nothing stands out as being difficult in my memory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants