Unexpected Removal of Runner from Production After VM Shutdown

[Sidharth-Chandra]

After shutting down and restarting the Dev and QA VM hosting our self-hosted runner, the Dev and QA runners were unexpectedly removed from the runner's list. We have been following this process for several months without any issues, but this behavior happened for the first time. Production is currently inactive but still accepting jobs.

Steps to reproduce the behavior:

1. Have a self-hosted runner running on a VM.
2. Shut down the VM.
3. Restart the VM and check the runner status.
4. Observe that the runner has been removed.

Expected behavior The runner should persist after a VM restart and automatically reconnect upon boot, as it has done in the past.

Runner Version and Platform Platform: linux

[TingluoHuang]

Can you share the runner diag log? 🙇

[bylidev]

Maybe you are not properly binding some required files

-rw-r--r-- 1 runner 1001 268 Apr 7 22:45 .credentials -rw------- 1 runner 1001 1667 Apr 7 22:45 .credentials_rsaparams

I changed the entrypoint to fix this problem https://github.com/byli-dev/github-runner