-
Notifications
You must be signed in to change notification settings - Fork 147
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
New install on Mac M3Max - gitlab runner fails. #2187
Comments
Thanks. Will try.
The only error I have is what is in the initial report. It is repeated 30 times and then the container fails. The key error seems to be:
|
hey @paxinos just a note to confirm that we have recreated and appreciate the report, we'll report back once we have a workaround and will patch in the next drop. looks like gitlab-runner registration had a recent breaking change that bit us. |
Thanks @johndietz ! Appreciated! Glad to know it wasn't me ;-) |
Hey @paxinos, thanks for reporting this issue. I can confirm this has been fixed in v2.4.12. |
Great... Thanks. But:
(base) ***@***.*** kubefirst (⎈|vinzini:N/A)]$ kubefirst version
A newer version (v2.4.12) is available! Please upgrade with: "brew update
&& brew upgrade kubefirst"
kubefirst-cli golang utility version: v2.4.12
(base) ***@***.*** kubefirst (⎈|vinzini:N/A)]$
Message ID: ***@***.***>
… |
Oops, we were too fast to celebrate this issue fixed. The new CLI isn't available on Homebrew yet: Homebrew/homebrew-core#177411 |
Which version of kubefirst are you using?
2.4.8
Which cloud provider?
k3d (local)
Which DNS?
None specific
Which installation type?
CLI
Which distributed Git provider?
GitLab
Did you use a fork of
gitops-template
?No
Which Operating System?
macOS
What is the issue?
Tried a couple times with the same results.
Command line is:
kubefirst k3d create --git-provider gitlab --gitlab-group theosis1 --cluster-name theosis1
Verfied gitlab-token is valid and has proper permissions.
Another Mac issue is when using bash as the shell, if kubefirst exits I need to run 'stty sane' or else the shell behaves poorly (doesn't use newlines/returns,... doesn't show cursor,.... )
Code of Conduct
The text was updated successfully, but these errors were encountered: