You are here: Maschinenraum » BuildServer

Build Server

Stand 29.03.2026

Hardware, Standort

Server Standort CPU Passmark
Server von Andi H. 2x AMD-EPYC-7601 ~70000 (weil 2 CPUs)
"Von Cawi" Gatrobe Intel Xeon E5-2620 v4 @ 2.10GHz 9231
"Backupserver über Förderung der LHH" ungenutzt, liegt im Lab auf dem Schrank Intel Core i7-13700F 37971
https://www.cpubenchmark.net/compare/5163vs2766vs3142/Intel-i7-13700F-vs-Intel-Xeon-E5-2620-v4-vs-AMD-EPYC-7601

Adding a slave

Step 1 - Install Forgejo Runner as Containerized Setup

https://forgejo.org/docs/v11.0/admin/actions/runner-installation/#oci-image-installation

Step 2 - Allow access to docker-in-docker (aka. dind) inside build to build containers

Edit the file data/config.yml

runner:
  # … skipping other configuration values you may have …
  envs:
    # Step 3 (Part 1):
    # A container will be setup for each job, and each step will
    # be executed in it.
    # This DOCKER_HOST environment variable will be used at each exec
    # in that container, like docker exec -e DOCKER_HOST=tcp://dind_container.docker.internal:2375 <command>
    # When you run the docker CLI or related
    # commands, they'll find this variable and reach out to the DIND
    # container to perform work there.
    DOCKER_HOST: tcp://dind_container.docker.internal:2375
  # … skipping …

container:
  # … skipping ...
# # Step 3 (Part 2): # DNS resolve `dind_container` in the context of the container's # host (the DIND container) to allow tcp://... to find it. options: '--add-host=dind_container.docker.internal:host-gateway' # … skipping ...

Inspired by https://forgejo.org/docs/next/admin/actions/docker-access/#configuration
Impressum -- Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
This website is using cookies. More info. That's Fine