Files
cluster-knaster/deploy/gitea-runner/docker-compose.yml
T
rorappandClaude Opus 5.5 0533f224f1
ci / test (push) Successful in 24s
deploy: Runner-Speicherlimit 1G (256M führte zu OOM-Kills)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 01:30:32 +02:00

43 lines
1.5 KiB
YAML

# Gitea Actions Runner (act_runner) für cluster-knaster als Swarm-Stack (Portainer).
# Gleiches Muster wie der vorhandene Stack "gitrunner": Token als Swarm-Secret, Konfiguration als Swarm-Config.
# Vorher anlegen:
# docker secret create gitea-runner-knaster-token <datei-mit-token>
# docker config create gitrunner_knaster_config_v1 config.yaml
services:
runner:
image: docker.io/gitea/act_runner:0.2.11
environment:
CONFIG_FILE: /config.yaml
GITEA_INSTANCE_URL: ${GITEA_INSTANCE_URL:-https://gitea.mindboost.team}
GITEA_RUNNER_REGISTRATION_TOKEN_FILE: /run/secrets/gitea-runner-knaster-token
GITEA_RUNNER_NAME: ${GITEA_RUNNER_NAME:-knaster-runner-01}
GITEA_RUNNER_LABELS: ${GITEA_RUNNER_LABELS:-ubuntu-latest:docker://node:20-bookworm}
secrets:
- gitea-runner-knaster-token
configs:
- source: runner_config
target: /config.yaml
volumes:
- runner_data_knaster:/data
- /var/run/docker.sock:/var/run/docker.sock # startet die Job-Container auf diesem Host
deploy:
mode: replicated
replicas: 1
restart_policy: {condition: any, delay: 10s}
placement:
constraints: [node.role == manager]
resources:
limits: {cpus: "1", memory: 1G} # 256M reichte nicht (OOM-Kill beim Job-Start)
secrets:
gitea-runner-knaster-token:
external: true
configs:
runner_config:
external: true
name: gitrunner_knaster_config_v1
volumes:
runner_data_knaster: