4 ms·
Sure. Constructing the case to shoot yourself in the foot is not a big problem. But in reality things mostly just work. I’m happily running a bunch of services
by jwildeboer 1y ago
Sure. Constructing the case to shoot yourself in the foot is not a big problem. But in reality things mostly just work. I’m happily running a bunch of services behind a (nginx) reverse proxy as rootless containers. Forgejo, the forgejo runner to build stuff, uptime-kuma and more on a bunch of RHEL10 machines with SELinux enabled.
- preisschild 1y agoDo you do OCI/container builds inside your forgejo-runner container?
- mfenniak 1y agoPeople having trouble getting this configured is a common issue for self-hosting Forgejo Runner. As a Forgejo contributor, I'm currently polishing up new documentation to try to support people with configuring this; here's the draft page: https://forgejo.codeberg.page/@docs_pull_1421/docs/next/admin/actions/docker-access/ https://forgejo.codeberg.page/@docs_pull_1421/docs/next/admi... (Should live at https://forgejo.org/docs/v12.0/admin/actions/docker-access/ https://forgejo.org/docs/v12.0/admin/actions/docker-access/ once it is finished up, if anyone runs into the comment after the draft is gone.)
- preisschild 1y agoIm not hosting a Forgejo instance (yet), but self-hosted Gitlab with gitlab-runner in Kubernetes, so I was wondering how you solved this. I'm using dind too, but this requires privileged runners...