zarko-a

Bump... Did anyone find a solution to this problem? Same issue with any browser.

Thanks @manuelschneider , unfortunately this did not work for me, after commenting out that line I got user not provision error.

Thank you, and thank you for making Firefly III.

Same issue with Pomerium reverse proxy. I just get redirected to the login page even though the proxy is sending user in `Remote-User` header ``` LD_ENABLE_AUTH_PROXY: True LD_AUTH_PROXY_USERNAME_HEADER: HTTP_REMOTE_USER ```...

We've experienced the same issue with `requiredDuringSchedulingIgnoredDuringExecution` ``` affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: node-role.kubernetes.io/spot-worker operator: DoesNotExist ``` Pods never get scheduled even though nodes don't have the...

hi @nikola-jokic . Is there an official plan and ETA to move away from RWX volumes when `ACTIONS_RUNNER_USE_KUBE_SCHEDULER` is enabled ? The current pairing of runner and job/workflow pods makes...

@LeonoreMangold Besides having RWX volumes, you need to set `ACTIONS_RUNNER_USE_KUBE_SCHEDULER` to true in runner scaleSet values file (assuming it's installed via Helm chart). That worked for us with NFS backed...

I stand corrected, it looks like it was released 5 hours ago. https://github.com/actions/runner-container-hooks/releases/tag/v0.8.0

The same issue started for us yesterday. No errors in ARC controller or listener logs. Everything appears fine except for the fact that the queued job doesn't start.

Another workaround that might be better if you are using kubernetes driver for buildx is to not use `aws-actions/amazon-ecr-login` and use https://github.com/docker/login-action instead. It supports Pod Identity out-of-the box and...