self-hosted action runner failed to update
See original GitHub issueDescribe the bug
I am running GitHub action runner inside a docker container (DinD). When a new runner version is available, runner tries to upgrade itself and for this I am already running ./bin/runsvc.sh
as the entrypoint process. But runner upgrade fails with error(mentioned below).
To Reproduce Steps to reproduce the behavior:
- Go to https://github.com/karancode/ghar
- please set the github repo name, token, etc. and build the docker Dockerfile. Make sure to set an older runner version.
- run the docker container and let the runner upgrade its version.
Expected behavior Runner version should be upgraded successfully and container process should also survive.
Runner Version and Platform
Tried with runner version v2.262.1
(or any older version).
Running on Ubuntu 18.04
docker image.
What’s not working?
# Authentication
√ Connected to GitHub
# Runner Registration
√ Runner successfully added
√ Runner connection is good
# Runner settings
√ Settings Saved.
.path=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Starting Runner listener with startup type: service
Started listener process
Started running service
√ Connected to GitHub
2020-06-21 08:28:53Z: Listening for Jobs
Runner update in progress, do not shutdown runner.
Downloading 2.263.0 runner
Waiting for current job finish running.
Generate and execute update script.
Runner will exit shortly for update, should back online within 10 seconds.
/_work/_update.sh: line 96: /bin/mv: No such file or directory
Runner listener exited with error code 3
Runner listener exit because of updating, re-launch runner in 5 seconds.
Starting Runner listener with startup type: service
Started listener process
events.js:187
throw er; // Unhandled 'error' event
^
Error: spawn /bin/Runner.Listener ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'spawn /bin/Runner.Listener',
path: '/bin/Runner.Listener',
spawnargs: [ 'run', '--startuptype', 'service' ]
}
Please help me out here 🙇
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Cannot update GITHUB_PATH on self-hosted windows ...
a possible solution is to reinstall the self-hosted runner as a user and make sure this user has the specific permissions you need....
Read more >Self-hosted runners can now disable automatic updates
GitHub Actions: Self-hosted runners can now disable automatic updates. You now have more control over when your self-hosted runners perform ...
Read more >Self-Hosted runner on Kubernetes : r/github
I keep getting this error on the controller. 2023-03-29T21:35:44Z DEBUG events Updating registration token failed {"type": "Warning", "object": ...
Read more >Updating the self-hosted GitHub runner - Damir's Corner
The automatic update for the self-hosted GitHub runner fails when it's running in a container, and causes it to stop. I couldn't find...
Read more >Create your Self-Hosted Github Action Runner in 5 minutes
For that, I found the always() workflow function extremely helpful. This last step will always run, even if a previous step failed. steps:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@TingluoHuang is there any update? or anything I should check for ?
I’m going to close out this issue until we hear back from you, please let us know if you are still seeing this issue!