Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] First impressions

Hi Eugene,


Thank you for the prompt response!


Indeed, disabling SELinux resolved Issue #1 - when working on the zipped installation.


I will later try again reproducing Issue #2 - when using the docker installation. If it happens again I will submit an issue as you've suggested.


Thanks,

Kaloyan



From: che-dev-bounces@xxxxxxxxxxx <che-dev-bounces@xxxxxxxxxxx> on behalf of Eugene Ivantsov <eivantsov@xxxxxxxxxxx>
Sent: Sunday, January 31, 2016 10:13 AM
To: che developer discussions
Subject: Re: [che-dev] First impressions
 
Hello!

Can you register an issue here please - https://github.com/codenvy/che/issues so that we can track it?
github.com
che - High performance developer environments in the cloud


As to your issues - cannot allocate memory speaks for itself, although system load indicator says it has plenty of RAM. How much ram do you have?

Your other issue can be caused by https://github.com/codenvy/che/issues/232

Can you verify is SELinux is disabled?

Also, I have just run Che in Docker, created a workspace, stopped the server (which shut down the container), the ran docker start che, and my workspace with a sample project was there. I did not shut down my machine though.. so maybe abnormal shutdown caused the problem. Can you repeatedly reproduce this behavior with Che in Docker?

On Sun, Jan 31, 2016 at 9:45 AM, Kaloyan Raev <kaloyan.r@xxxxxxxx> wrote:

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


_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev




--

Eugene Ivantsov | Docs&Support |eivantsov@xxxxxxxxxxx

Back to the top