We've been running our platform for a couple of months now, and overall it's been going good - but one thing we haven't been able to solve is running self-hosted GitHub Action runners with #Docker.
We are running them as a scale group per GitHub repository (we have monorepos so we don't need many) then within that run 1 instance during 'office hours' and scale down to 0 with ad-hoc needs at the evenings and weekends.
Next we looked at adding it to our apt-get in our container image for the runners themselves - but we got a very particular error about the --output argument not being supported, despite it being clear in the docs - well we since found out that this choice offers 7 levels of dependency hell.
Because the GitHub Action runner is currently based on Ubuntu 22.04, the version in it's repo is 1.23.1 - Ubuntu 24.04 has version 1.33.7 (LOL) which supports the --output argument
I also don't like the idea of building from source in an image (would definitely separate to a build pipeline and store a binary in our repo or storage account).
Anyway, we decided to call it a day so I'm here to ask - has anyone else solved this problem, and how? (Thanks in advance) - we really have other things to get on with and this seems like it shouldn't be this hard.
I am excited to present at the Dev AI conference in Paris on June 19!
I am going to run a workshop about the deployment and monitoring of ML pipelines with free and open-source tools. This includes using tools such as GitHub Actions and Pages, Docker, Python, Quarto, etc.
Vous auriez des préconisations best practice pour utiliser docker et produire des images pour des applications tournants dans un tomcat ?
J'avais dans ma todo list
Just switched my #SelfHosted#PeerTube instance from using #Redis to #Valkey now that it has a stable release out as a #Docker#container too, and.. that went too easily 😅. I know this makes sense as it is 100% compatible, but it still feels quite amazing to have it just work.
In case it helps; I just switched to using the valkey/valkey:7-alpine image, and because I also renamed things in my docker-compose I added PEERTUBE_REDIS_HOSTNAME=valkey to the PeerTube .env file too. That's it!
@kfdm hard agree.
The "plugin" economy on GitHub is insane. I find it very tedious and complicated to figure out how to plug together my pipeline. And ultimately it's still running containers, so there's no need to make everything so convoluted.
Meanwhile, if you've ever worked with a Dockerfile, you can plug together a Woodpecker pipeline in no time. 🙂