-
-
Notifications
You must be signed in to change notification settings - Fork 331
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
Error creating instance - Hostname too long #536
Comments
Same problem here. Tried the update today and it failed. |
Same here, have managed to figure out how to solve it? I tried downgrading but an older version but that didn't help. |
No solution so far. Downgrading to 5.1.0 worked here. Using shorter hostnames is also not working. The machine is created and dies seconds later. |
Hmm, strange. Shortening the hostname works now.
Setting a short value for |
Did some analysis on one of my runners:
Thus the maximum user defined part of the hostname is 64-35-1=28 characters ( Example:
The runners are named like |
Bumping into this problem today. Anyone know when the fix will be released? |
Same problem here. |
I am running into this bug too. For now I've downgraded to |
🎉 This issue has been resolved in version 5.3.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
v5.2.0+ creates runner instances with very long names, eg.
runner-2stajshg-gitlab-runner-beefy-docker-machine-1661510762-2a25d6d4
(wheregitlab-runner-beefy
is our environment name). This causes the instances to fail to create with the following errors in CloudWatch:The text was updated successfully, but these errors were encountered: