| [che-dev] First impressions |
|
Hi,
I am playing with Che for the last couple of days. I am really excited how Che redefines the concept of the workspace.
I faced some issue that I believe are more configuration problems on my side rather than real bugs. I will be thankful if you give me some assistance. I am on Fedora 23 64-bit and I am using the latest stable version of Che - 4.0.0-beta-13.
Issue #1. Cannot start a workspace when using the zipped installation.
I download the zip archive, extract it and start it with "bin/che.sh run". I can access the dashboard, but when I try to create a new project, the workspace fails to start. See the attached screenshot workspace-start-error-1.png.
If I try to start it again then I get a more descriptive error: "[STDERR] nsenter: Unable to fork: Cannot allocate memory." See the attached screenshot workspace-start-error-2.png.
I don't get this problem if I launch Che as a Docker container, but then I get Issue #2.
Issue #2. I lose all workspaces and projects when restarting the Docker container.
Due to Issue #1, I started Che as a Docker container. I was able to play for a few hours creating some workspaces and projects. Then I had to restart my laptop. I launcher the same Docker container using "docker run che". It started successfully, but all my workspaces and projects that I created before the laptop restart are lost, which was quite disappointing.
If I start again the tarball installation I can see that it persists the workspaces that fail starting due to Issue #1. So it seems I have some configuration problem when running Che as a Docker container.
Thanks in advance for your assistance. Kaloyan |
Attachment:
workspace-start-error-1.png
Description: workspace-start-error-1.png
Attachment:
workspace-start-error-2.png
Description: workspace-start-error-2.png
