Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Initializing containers fails on self-hosted runners
See original GitHub issueDescribe the bug
Our self hosted actions runner stopped working correctly during the step “Initialize Containers” and threw out an error message Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.40/version: dial unix /var/run/docker.sock: connect: permission denied. It was first observed in https://github.com/DimensionDev/Maskbook/runs/669343239?check_suite_focus=true.
We migrated our almost all CI jobs to actions on our self hosted runner in this PR and it worked just fine.
To Reproduce I don’t know if this can be reproduced on other machines but I can provide the specs of our machine:
Ubuntu 18.04 on AWS
4 Core 8GB Mem
Expected behavior It initializes the container correctly.
Runner Version and Platform
Neither 2.165.2 nor 2.262.1 works
Ubuntu 18.04
What’s not working?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We’ve been encountering this problem earlier this week. Migrating to Ubuntu focal seems to have fix it. Then we had to adjust docker privileges and restart the runner process (see this link)
@yisiliu make sure your runner’s run-as account has permission to execute docker command without
sudohttps://docs.docker.com/engine/install/linux-postinstall/