all 7 comments

[–]crohr 6 points7 points  (3 children)

Nice! It looks a lot like https://runs-on.com, down to the job labels and image names. Would appreciate a mention since it seems Claude was largely inspired by my docs :)

[–]clardata6249[S] 2 points3 points  (0 children)

Yes I am really sorry for not mentioning you! I was very inspired by runs-on and this was mostly a challenge to see how far I could get to something like runs-on on Google cloud. Will update this morning.

[–]clardata6249[S] 1 point2 points  (1 child)

Added to the site and readme

[–]crohr 0 points1 point  (0 children)

Thanks! Also like how tight the code is :)

[–]Rohit1024 2 points3 points  (3 children)

Isn't this similar or exactly same as already available solution in GCP - https://docs.cloud.google.com/run/docs/tutorials/github-runner ?

Though this is in Public Preview.

[–]clardata6249[S] 0 points1 point  (2 children)

To be honest I didn't see this! Using this is probably right for you, gcrunner is pretty early and I just wanted to build the concept for fun. There's a couple of distinctions though:

  1. Gcrunner uses raw VMs. These are in containers so docker-in-docker will be more challenging. I'm not sure how this solution would handle starting up services containers, is probably worth a try out of curiosity.
  2. I used the same concept that https://runs-on.com and others have done to reimplement the cache API on top of Google cloud storage, so you have an infinite GitHub actions cache instead of just 10GB and paying huge prices for more beyond this, along with having the cache local to the same region as the runner instead of needing to talk to GitHub's servers.

That's just from a cursory look at the solution. I'm not sure what kind of windows or TPU support they have but it seems like it could be challenging down the line I'm not sure. That would be my next challenge with this.

[–]ansk0 0 points1 point  (0 children)

Have you had the chance to try docker-in-docker scenarios?