networks: test-net: driver: bridge name: gitops-test-network volumes: forgejo-data: driver: local driver_opts: type: none o: bind device: ${PWD}/forgejo_data runner-data: driver: local driver_opts: type: none o: bind device: ${PWD}/runner_data services: # 1. FORGEJO (Git Server + Registry) forgejo: image: data.forgejo.org/forgejo/forgejo:9 container_name: forgejo networks: - test-net environment: - FORGEJO__SERVER__HTTP_PORT=3000 - FORGEJO__SERVER__ROOT_URL=http://localhost:3000 - FORGEJO__ACTIONS__ENABLED=true - FORGEJO__PACKAGES__ENABLED=true - FORGEJO__PACKAGES__CONTAINER_ENABLED=true ports: - "3000:3000" - "3005:3000" - "2222:22" volumes: - forgejo-data:/data restart: always # 2. FORGEJO RUNNER (Pipeline-Ausführung) forgejo-runner: image: data.forgejo.org/forgejo/runner:9 container_name: forgejo-runner networks: - test-net user: "0:0" entrypoint: ["/bin/sh", "-c"] command: ["forgejo-runner daemon"] environment: - GITEA_INSTANCE_URL=http://forgejo:3000 - GITEA_RUNNER_REGISTRATION_TOKEN=z6xlwg3dSRYZ59zUxfrztDJasG6VkvulFyTwtJQS - GITEA_RUNNER_NAME=debian-local-runner - GITEA_RUNNER_LABELS=ubuntu-latest:docker://debian:stable-slim,debian-stable:docker://debian:stable-slim volumes: - /var/run/docker.sock:/var/run/docker.sock - runner-data:/data - ./kind_kubeconfig:/root/.kube # Reicht die K3s-Config an Terraform weiter depends_on: - forgejo restart: always # 3. KUBERNETES PLATTFORM (K3s: Voll kompatibel mit Devuan/elogind) k3s-cluster: image: rancher/k3s:v1.28.2-k3s1 container_name: local-k3s-platform networks: - test-net privileged: true tmpfs: - /run - /var/run ports: - "8443:6443" # Kubernetes-API für dein lokales Terraform - "8080:80" # Hierüber erreichst du deine Webapp-Updates von aussen environment: - K3S_KUBECONFIG_OUTPUT=/output/config - K3S_KUBECONFIG_MODE=666 volumes: - ./kind_kubeconfig:/output # Schreibt die Zugangsdaten direkt in dein Projektverzeichnis command: server --disable traefik --egress-selector-mode=disabled restart: always