Self-hosted runner goes offline after host reboot#16

Answered by tvoronovrafaelcosta asked this question in Pipelinesrunners pipelines

rafaelcosta4d ago

12

4 Answers

tvoronov3d ago

12

lena-sch2d ago

0

Suggested topics

1 reply

rafaelcostaAuthor2d ago

Perfect, running as a service now.

0

1 reply

tvoronovyesterday

On macOS svc.sh installs a launchd agent instead — same commands.

0

Cache restore misses every run after switching to a matrix build3 replies

Secrets are empty in pull requests from forks2 replies

Our docs site now deploys on every merge in 38 seconds2 replies

Solved by tvoronov

Install it as a service instead of running run.sh: sudo ./svc.sh install lattice-runner sudo ./svc.sh start systemctl status lattice.runner.* The service unit restarts it on boot and on crash.

Jump to post

Our self-hosted runner on Ubuntu 24.04 shows Offline after every reboot until I log in and start it by hand. I installed it with ./config.sh. How do I make it survive a reboot?

Install it as a service instead of running run.sh:

sudo ./svc.sh install lattice-runner
sudo ./svc.sh start
systemctl status lattice.runner.*

The service unit restarts it on boot and on crash.

Bookmarking this. Does the same work on macOS?

Self-hosted runner goes offline after host reboot#16

4 Answers

Related topics

Suggested topics