Alec Cunningham

FWIW our org does this today for both the docker volume and workspace ```yaml volumes: - name: tool-cache persistentVolumeClaim: claimName: tool-cache-enterprise-runnerset-0 - name: work ephemeral: volumeClaimTemplate: spec: accessModes: [ "ReadWriteOnce"...

Old but I just ran into the same problem. This is applicable on the `jetbrains/teamcity-agent:2021.1.2-linux-sudo` image. I was able to fix it as follows: Firstly, you need to grab `agent.sh`...

Old but I just ran into the same problem. This is applicable on the `jetbrains/teamcity-agent:2021.1.2-linux-sudo` image. I was able to fix it as follows: Firstly, you need to grab `agent.sh`...

@synack-badamson are you aware if we have access to the org and repo in the pre-run hooks? Applying a label with this information would be very useful to me

> > @synack-badamson are you aware if we have access to the org and repo in the pre-run hooks? Applying a label with this information would be very useful to...

I solved this by using a `ReadWriteMany` PVC that every ephemeral runner attaches to upon startup: ```yaml apiVersion: actions.summerwind.dev/v1alpha1 kind: RunnerSet metadata: name: enterprise-runnerset-large spec: replicas: 4 image: $IMAGE dockerdWithinRunnerContainer:...

@adiroiban how would that work with multiple nodes in the cluster? Each time a runner comes online it would have a different cache - my first pass used this but...

@davidwincent there is a actively maintained project for exactly that I came across quite recently; have not tried it myself, however https://github.com/falcondev-oss/github-actions-cache-server

Any updates here? We expose a central grafana that aggregates hundreds of prometheus instances, and do not expose Prometheus. This would be a great way to connect the two systems.