-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
chectl server:deploy fails on fresh minikube installation #21862
Comments
I can suggest the following:
|
And again with --skip-cert-manager:
|
I see, it fails again on the step when tries to reach github.com server. Is github.com available?
|
Gets a little bit farther, it seems. Failing at creating Dex certificate, now.
After step 1 above:
|
To be honest I have no idea what is going on. |
The "error" I'm getting certainly doesn't make any sense to me either; it appears to just vomit out a config file of sorts... Running your suggestions. Doesn't look like anything is restarting unexpectedly.
Then ran
Further details. Trying to think of anything else that may matter. Focusing only on my Linux box, but can do whatever in Windows, too. Whatever works best for getting the information to troubleshoot. This was all done to install Che. This server has only been running AMP, and only what was required for the game servers. No other services, so mostly sitting idle. No local firewall. Full internet connectivity, with DNS server hosted on LAN. The TCP errors make me want to think it's network...but i realize that could just be what shows up, not the actual error. Docker installed via apt: `apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin' from instructions here: https://docs.docker.com/engine/install/debian/ Exactly
Just for kicks, ran `chectl server:deploy -p minikube --debug``` and got the same result, which I expected. I had an error before that I tracked down to #4172, so have tried with kubernetes 1.23.12 and 1.23.14 with the same results in a VM, though I don't recall which OS in those cases. A couple times, apparently randomly, Che WOULD deploy; I'd first attributed this error to a pure connection issue, and thought that if I waited for all the minikube/kubernetes services to come up and stabilize, it would be fine. That doesn't appear to be the case, as you can see by the outputs above. Checked apt, and there was an update to containerd.io available (1.6.11-1, had 1.6.10-1). Applied that, restarted minikube (same command as above). No change. |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Summary
Not entirely sure if this is a Che issue or minikube or somewhere between them.
Following instructions here: https://www.eclipse.org/che/docs/stable/administration-guide/installing-che-on-minikube/
After executing
chectl server:deploy --platform minikube
I get the followingRelevant information
Running on bare metal: Dell Poweredge R620. Dual Xeon E5-2637, 64GB RAM, Debian 11.
I am brand new to Kubernetes, and trying everything I can think of to get Che running. I've had this same error on Fedora in a VM, Ubuntu in a VM, and Windows 10 (using Docker in the Linux flavors, Hyper-V with Windows)
Windows 10 yields a slightly different failure, but the rest seems the same.
The text was updated successfully, but these errors were encountered: