add changes

Gitea-webserver.kube.yaml

@@ -106,7 +106,8 @@ spec:
         - name: GITEA_INSTANCE_URL
           value: "https://gitea.tryton.geeraert.eu/"
         - name: GITEA_RUNNER_REGISTRATION_TOKEN
-          value: "2lLHg3Zt4mqjz04cBVIi6UI11cDOwIrwvNY6FMTH"
+#          value: "2lLHg3Zt4mqjz04cBVIi6UI11cDOwIrwvNY6FMTH"
+          value: "95NWFriTQnu910SpcbteDybyi9X5LffdLdaTK8lk"
         - name: GITEA_RUNNER_NAME
           value: "runner"
         - name: GITEA_RUNNER_LABELS
@@ -134,6 +135,48 @@ spec:
           name: gitea-runner-configfile
           defaultMode: 0555
 
+
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: remote-buildkitd
+  namespace: gitea
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: remote-buildkitd
+  template:
+    metadata:
+      labels:
+        app: remote-buildkitd
+    spec:
+      nodeName: kube-master
+      containers:
+      - name: remote-buildkitd
+        image:  moby/buildkit:latest
+        securityContext:
+          privileged: true
+          runAsUser: 0
+        imagePullPolicy: IfNotPresent
+        ports:
+        - containerPort: 1234
+          name: buildkitd-port
+        volumeMounts:
+        - name: remote-buildkitd-data
+          mountPath: /etc/buildkit/certs
+        resources:
+            limits:
+#              cpu: 500m
+              memory: 1000Mi
+      volumes:
+      - name: gitea-var-docker-sock
+        hostPath:
+           path: /var/run/docker.sock
+      - name: remote-buildkitd-data
+        persistentVolumeClaim:
+          claimName: remote-buildkitd-data
 ---
 apiVersion: v1
 kind: Service
@@ -147,3 +190,18 @@ spec:
       protocol: TCP
   selector:
     app: gitea-webserver
+
+
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: buildkitd
+  namespace: gitea
+spec:
+  ports:
+    - port: 1234
+      targetPort: buildkitd-port
+      protocol: TCP
+  selector:
+    app: remote-buildkitd

config.yaml

@@ -39,10 +39,11 @@ runner:
   # If it's empty when execute `daemon`, will use labels in `.runner` file.
   labels:
     - "ubuntu-latest:docker://gitea/runner-images:ubuntu-latest"
-    - "ubuntu-latest:docker://debian:stable-slim"
+    - "custom-runner-debian-slim:docker://gitea.tryton.geeraert.eu/pi-ux-ce/custom-runner-debian-slim:latest"
-    - "host-runner:host"
     - "ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04"
     - "ubuntu-20.04:docker://gitea/runner-images:ubuntu-20.04"
+#    - "ubuntu-latest:docker://debian:stable-slim"
+    - "host-runner:host"
 
 cache:
   # Enable cache server to use actions/cache.

config.yaml.save

@@ -0,0 +1,105 @@
+# Example configuration file, it's safe to copy this as the default config file without any modification.
+
+# You don't have to copy this file to your instance,
+# just run `./act_runner generate-config > config.yaml` to generate a config file.
+
+log:
+  # The level of logging, can be trace, debug, info, warn, error, fatal
+  level: info
+
+runner:
+  # Where to store the registration result.
+  file: .runner
+  # Execute how many tasks concurrently at the same time.
+  capacity: 1
+  # Extra environment variables to run jobs.
+  envs:
+    A_TEST_ENV_NAME_1: a_test_env_value_1
+    A_TEST_ENV_NAME_2: a_test_env_value_2
+  # Extra environment variables to run jobs from a file.
+  # It will be ignored if it's empty or the file doesn't exist.
+  env_file: .env
+  # The timeout for a job to be finished.
+  # Please note that the Gitea instance also has a timeout (3h by default) for the job.
+  # So the job could be stopped by the Gitea instance if it's timeout is shorter than this.
+  timeout: 3h
+  # The timeout for the runner to wait for running jobs to finish when shutting down.
+  # Any running jobs that haven't finished after this timeout will be cancelled.
+  shutdown_timeout: 0s
+  # Whether skip verifying the TLS certificate of the Gitea instance.
+  insecure: false
+  # The timeout for fetching the job from the Gitea instance.
+  fetch_timeout: 5s
+  # The interval for fetching the job from the Gitea instance.
+  fetch_interval: 2s
+  # The labels of a runner are used to determine which jobs the runner can run, and how to run them.
+  # Like: "macos-arm64:host" or "ubuntu-latest:docker://gitea/runner-images:ubuntu-latest"
+  # Find more images provided by Gitea at https://gitea.com/gitea/runner-images .
+  # If it's empty when registering, it will ask for inputting labels.
+  # If it's empty when execute `daemon`, will use labels in `.runner` file.
+  labels:
+    - "ubuntu-latest:docker://gitea/runner-images:ubuntu-latest"
+    - "ubuntu-latest:docker://debian:stable-slim"
+    - "ubuntu-latest:docker://debian:stable-slim"
+    - "host-runner:host"
+    - "ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04"
+    - "ubuntu-20.04:docker://gitea/runner-images:ubuntu-20.04"
+
+cache:
+  # Enable cache server to use actions/cache.
+  enabled: true
+  # The directory to store the cache data.
+  # If it's empty, the cache data will be stored in $HOME/.cache/actcache.
+  dir: ""
+  # The host of the cache server.
+  # It's not for the address to listen, but the address to connect from job containers.
+  # So 0.0.0.0 is a bad choice, leave it empty to detect automatically.
+  host: ""
+  # The port of the cache server.
+  # 0 means to use a random available port.
+  port: 0
+  # The external cache server URL. Valid only when enable is true.
+  # If it's specified, act_runner will use this URL as the ACTIONS_CACHE_URL rather than start a server by itself.
+  # The URL should generally end with "/".
+  external_server: ""
+
+container:
+  # Specifies the network to which the container will connect.
+  # Could be host, bridge or the name of a custom network.
+  # If it's empty, act_runner will create a network automatically.
+  network: ""
+  # Whether to use privileged mode or not when launching task containers (privileged mode is required for Docker-in-Docker).
+  privileged: false
+  # And other options to be used when the container is started (eg, --add-host=my.gitea.url:host-gateway).
+  options: '--volume /mnt/runner-cache:/toolcache'
+  # The parent directory of a job's working directory.
+  # NOTE: There is no need to add the first '/' of the path as act_runner will add it automatically. 
+  # If the path starts with '/', the '/' will be trimmed.
+  # For example, if the parent directory is /path/to/my/dir, workdir_parent should be path/to/my/dir
+  # If it's empty, /workspace will be used.
+  workdir_parent:
+  # Volumes (including bind mounts) can be mounted to containers. Glob syntax is supported, see https://github.com/gobwas/glob
+  # You can specify multiple volumes. If the sequence is empty, no volumes can be mounted.
+  # For example, if you only allow containers to mount the `data` volume and all the json files in `/src`, you should change the config to:
+  valid_volumes:
+    - '/mnt/runner-cache/**'
+  #  - data
+  #  - /src/*.json
+  # If you want to allow any volume, please use the following configuration:
+  # valid_volumes:
+  #   - '**'
+#  valid_volumes: []
+  # overrides the docker client host with the specified one.
+  # If it's empty, act_runner will find an available docker host automatically.
+  # If it's "-", act_runner will find an available docker host automatically, but the docker host won't be mounted to the job containers and service containers.
+  # If it's not empty or "-", the specified docker host will be used. An error will be returned if it doesn't work.
+  docker_host: ""
+  # Pull docker image(s) even if already present
+  force_pull: false
+  # Rebuild docker image(s) even if already present
+  force_rebuild: false
+
+host:
+  # The parent directory of a job's working directory.
+  # If it's empty, $HOME/.cache/act/ will be used.
+  workdir_parent:

gitea-runner-configfile.configmap.yaml

@@ -23,10 +23,10 @@ data:
     \ # Find more images provided by Gitea at https://gitea.com/gitea/runner-images
     .\n  # If it's empty when registering, it will ask for inputting labels.\n  #
     If it's empty when execute `daemon`, will use labels in `.runner` file.\n  labels:\n
-    \   - \"ubuntu-latest:docker://gitea/runner-images:ubuntu-latest\"\n    - \"ubuntu-latest:docker://debian:stable-slim\"\n
+    \   - \"ubuntu-latest:docker://gitea/runner-images:ubuntu-latest\"\n    - \"custom-runner-debian-slim:docker://gitea.tryton.geeraert.eu/pi-ux-ce/custom-runner-debian-slim:latest\"\n
-    \   - \"host-runner:host\"\n    - \"ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04\"\n
+    \   - \"ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04\"\n    - \"ubuntu-20.04:docker://gitea/runner-images:ubuntu-20.04\"\n#
-    \   - \"ubuntu-20.04:docker://gitea/runner-images:ubuntu-20.04\"\n\ncache:\n  #
+    \   - \"ubuntu-latest:docker://debian:stable-slim\"\n    - \"host-runner:host\"\n\ncache:\n
-    Enable cache server to use actions/cache.\n  enabled: true\n  # The directory
+    \ # Enable cache server to use actions/cache.\n  enabled: true\n  # The directory
     to store the cache data.\n  # If it's empty, the cache data will be stored in
     $HOME/.cache/actcache.\n  dir: \"\"\n  # The host of the cache server.\n  # It's
     not for the address to listen, but the address to connect from job containers.\n

pvc.claim.yaml

@@ -37,8 +37,23 @@ spec:
   resources:
     requests:
       storage: 100Mi
----
 
+
+---
+kind: PersistentVolumeClaim
+apiVersion: v1
+metadata:
+  name: remote-buildkitd-data
+  namespace: gitea
+spec:
+  storageClassName: nfs-storage-intelligent
+  accessModes:
+    - ReadWriteMany
+  resources:
+    requests:
+      storage: 100Mi
+
+---
 kind: PersistentVolumeClaim
 apiVersion: v1
 metadata:

suggestion.txt

@@ -0,0 +1,44 @@
+container:
+  # ... other container options
+  valid_volumes:
+    - '/mnt/runner-cache/**'
+  options: '--volume /mnt/runner-cache:/toolcache' # Mount the host path to the job container's cache directory
+
+
+Method 1: Using the act_runner configuration file (config.yaml)
+You can define common volumes that should be mounted into all job containers in the runner's configuration file. 
+
+    Identify your host path: Determine the absolute path on the host machine where the PVC is mounted. In Kubernetes/Docker environments, this might be a specific path managed by your storage provider, or a directory you manually bound a volume to. Let's assume it is /mnt/runner-cache.
+    Edit config.yaml: Add the valid_volumes configuration under the container section of your config.yaml file to explicitly allow mounting that specific path. You can also specify common mounts for all jobs.
+    yaml
+
+    container:
+      # ... other container options
+      valid_volumes:
+        - '/mnt/runner-cache/**'
+      options: '--volume /mnt/runner-cache:/toolcache' # Mount the host path to the job container's cache directory
+
+    Use code with caution.
+
+    The options line uses standard Docker command-line syntax to add a volume mount: -v <host_path>:<container_path>.
+    /toolcache is the hardcoded default directory within the job container where the actions/cache and setup-* actions store their data.
+
+Restart the runner: For the changes to take effect, you must restart your act_runner container or service. 
+
+Method 2: Using the Workflow File (less ideal for central management)
+If you prefer per-workflow control, you can define the volume mount directly in the Gitea Actions workflow YAML file. This requires you to ensure the runner has permission to mount this path (which the docker.sock mapping usually implies).
+yaml
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    container:
+      image: your_job_image
+      volumes:
+        # Mount the host PVC path to the container cache path
+        - /mnt/runner-cache:/toolcache
+    steps:
+      # ... your steps using actions/cache
+
+Use code with caution.
+Ensure the Cache is Used in the Workflow