Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runners fail to register when IPs/hostnames are reused #128

Open
jeverling opened this issue Dec 8, 2022 · 4 comments · May be fixed by #127
Open

Runners fail to register when IPs/hostnames are reused #128

jeverling opened this issue Dec 8, 2022 · 4 comments · May be fixed by #127

Comments

@jeverling
Copy link

It seems that Github runners use the hostname as runner --name by default. This lead to runner instances not being able to register for us, because AWS was re-using internal IP addresses.
Setting runner --name explicitly to a unique value should fix this.

@karuppiah7890
Copy link

@jeverling I'm curious as to how this happened. Even if AWS was reusing internal IP addresses, and EC2 host names are based on it's private IP address, it can only cause two different EC2 hosts at different points in time to have the same host name. If that is the case, what's the problem here? Does GitHub expect new names every time a runner registers to GitHub and not reuse any old names used by old runners that don't exist anymore?

@jeverling
Copy link
Author

jeverling commented Aug 8, 2023

Does GitHub expect new names every time a runner registers to GitHub and not reuse any old names used by old runners that don't exist anymore?

Exactly, Github keeps a registry of runners, and refuses registering a runner with a name that has been used before. It might be possible to deregister runners or solve this in other ways, but I think using unique names for runners isn't a bad solution to this problem.

@karuppiah7890
Copy link

yeah, deregistering is a good way to solve the problem

@karuppiah7890
Copy link

Unique name is good in general 👍 I'm gonna use your solution for unique name

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants