Closed sravula84 closed 2 months ago
Hey @sravula84,
This is not an ARC issue. The error starts showing up when ARC applies your configuration. I would suggest you inspect the node and see why it can't register the bridge driver. When this stage is reached, the error is out of ARCs control.
Closing this one.
@sravula84 I'm hitting the same issue you describe in this when running on a Google Cloud Platform GKE cluster. The documentation offers no help into how to investigate this. I'm using the dind
container mode. Perhaps it simply won't work on GKE. Did you happen to solve your issue?
Looks like https://github.com/actions/actions-runner-controller/issues/3257 is related.
Checks
Controller Version
gha-runner-scale-set-0.9.0
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
1> installed runner scale set i can dind container but its failing with time="2024-04-11T17:36:43.038675049Z" level=info msg="stopping event stream following graceful shutdown" error="" module=libcontainerd namespace=moby │
│ time="2024-04-11T17:36:43.039373640Z" level=info msg="stopping healthcheck following graceful shutdown" module=libcontainerd │
│ time="2024-04-11T17:36:43.040084974Z" level=info msg="stopping event stream following graceful shutdown" error="context canceled" module=libcontainerd namespace=plugins.moby │
│ failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: unable to add return rule in DOCKER-ISOLATION-STAGE-1 chain: (iptables failed: iptables --wait -A DOCKER-ISOLATION-STAGE-1 -j RETURN: iptables v1.8.10 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain DOCKER-ISOLATION-STAGE-1 │
│ (exit status 4)) │
│ Stream closed EOF for arc-runners/prosper-linux-1-lpbvp-runner-fk69f (dind) │
Describe the expected behavior
docker:dind container should up and running
Additional Context
Controller Logs
Runner Pod Logs