Skip to content

Install on self-hosted runner fails on second run #205

@castorbarge

Description

@castorbarge

We use self-hosted runners in docker which stay running after running a job;

It appears that the tailscale github action (v4) does not remove or even stop the tailscaled service after finishing the job.
This causes an issue on consecutive runs, due to the tailscaled service being busy during install:

Cache restored successfully
Found Tailscale 1.88.3 in cache: /home/docker/actions-runner/_work/_tool/tailscale/1.88.3/Linux-amd64
▶️ copy tailscale from cache
/usr/bin/sudo cp /home/docker/actions-runner/_work/_tool/tailscale/1.88.3/Linux-amd64/tailscale /usr/local/bin/tailscale
▶️ copy tailscaled from cache
/usr/bin/sudo cp /home/docker/actions-runner/_work/_tool/tailscale/1.88.3/Linux-amd64/tailscaled /usr/local/bin/tailscaled
cp: cannot create regular file '/usr/local/bin/tailscaled': Text file busy
Error: sudo failed with exit code 1

A workaround in our case is to run pkill tailscaled at the end of the job.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions