"Cannot connect to the Docker daemon" after quickstart #2999
-
Followed the ARC 0.6.1 quickstart on a brand new cluster in Digital Ocean (1.28.2-do.0): NAMESPACE="arc-systems"
helm install arc \
--namespace "${NAMESPACE}" \
--create-namespace \
oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set-controller
INSTALLATION_NAME="arc-runner-set"
NAMESPACE="arc-runners"
GITHUB_CONFIG_URL="redacted"
GITHUB_PAT="redacted"
helm install "${INSTALLATION_NAME}" \
--namespace "${NAMESPACE}" \
--create-namespace \
--set githubConfigUrl="${GITHUB_CONFIG_URL}" \
--set githubConfigSecret.github_token="${GITHUB_PAT}" \
oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set I'm able to trigger a job and the runner starts, but it immediately fails under the 'Initialize Containers' step with:
Some potentially relevant bits of the runner pod logs:
Anybody else run into the same issue, or able to reproduce on a new DOKS cluster? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
Hey @alechartung, Your setup does not include dind so the docker socket is not mounted on the runner. To correctly set it up, you can follow the guide here |
Beta Was this translation helpful? Give feedback.
-
Hi guys, While using the latest config, this happens intermittently when there's high load on the runners computing pool (using regular dind)
We have resource limits on the dind container, but none on the runner (actual build is using dind). What would be the minimum limits for runner to mitigate this? |
Beta Was this translation helpful? Give feedback.
-
it might be different scenario, but I've described our case in issue: #3794 |
Beta Was this translation helpful? Give feedback.
Docs are updated☺️