Cannot start workspaces with custom plugin registry
See original GitHub issueDescribe the bug
I can’t start a workspace, if I use a custom Plugin registry. If I try to do so, I get this error:
Error: Failed to run the workspace: "Server 'theia' in container 'theia-ide4ig' not available."
I have done the following steps:
- build and deploy the custom plugin registry
- changed CHE_WORKSPACE_PLUGIN__REGISTR__URL in the configmap to the address of the custom plugin registry
- restartet the che pod via kubectl scale command
- tried to create and start a workspace
Che version
- latest
- nightly
- other: 7.4.0
Steps to reproduce
Expected behavior
Runtime
- kubernetes (include output of
kubectl version
)
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.4", GitCommit:"67d2fcf276fcd9cf743ad4be9a9ef5828adc082f", GitTreeState:"clean", BuildDate:"2019-09-18T14:51:13Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.4", GitCommit:"67d2fcf276fcd9cf743ad4be9a9ef5828adc082f", GitTreeState:"clean", BuildDate:"2019-09-18T14:41:55Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
- Openshift (include output of
oc version
) - minikube (include output of
minikube version
andkubectl version
) - minishift (include output of
minishift version
andoc version
) - docker-desktop + K8S (include output of
docker version
andkubectl version
) - other: (please specify)
Screenshots
Installation method
- chectl (chectl server:start -p minikube)
- che-operator
- minishift-addon
- I don’t know
Environment
- my computer
- Windows
- Linux
- macOS
- Cloud
- Amazon
- Azure
- GCE
- other (please specify)
- other: please specify
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Issues starting workspaces when DevWorkspace is enabled
Describe the bug I wanted to test the OpenShift connector with DevWorkspace enabled.
Read more >Troubleshoot WorkSpaces issues - AWS Documentation
Launching WorkSpaces fails with an internal error To check this setting, open the Amazon VPC console, select your subnet, and choose Subnet Actions,...
Read more >Chapter 3. Customizing the registries Red Hat CodeReady ...
3.3.2.1. Adding a custom plug-in registry using Command Palette · In the CodeReady Workspaces IDE, press F1 to open the Command Palette, or...
Read more >Eclipse workspace crashes on startup - Stack Overflow
I finally figured out JRebel plugin which seemed to be creating this problem. My JRebel license had expired and this plugin used to...
Read more >Customizing IBM Wazi Developer for Workspaces devfile, plug ...
Parent topic: Customizing Wazi Developer for Workspaces registry images ... Example source code for deploying a custom plug-in and devfile is available from ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for your help. I’ll close this issue now.
Good it’s working. It’s obviously not enough if it’s failing on
Insufficient memory
😃 I usually go with 6GB as a minimum for one workspace. Depends on the devfile though. Can we close this issue?