eclipse / che

Kubernetes based Cloud Development Environments for Enterprise Teams

Platform for providing Kubernetes-based Cloud Development Environments for Enterprise Teams

Che is Kubernetes-native and places everything the developer needs into containers in Kube pods including dependencies, embedded containerized runtimes, a web IDE, and project code. This makes workspaces distributed, collaborative, and portable to run anywhere Kubernetes runs ... Read More

---

Visit website at: https://eclipse.dev/che/ and documentation at: https://eclipse.dev/che/docs

• Getting Started
• Using Eclipse Che
• Feedback and Community
• Contributing
• Roadmap
• License

---

Getting Started

Here you can find links on how to get started with Eclipse Che:

• Use Eclipse Che online
• Run Eclipse Che on your own Kubernetes cluster

Using Eclipse Che

Here you can find references to useful documentation and hands-on guides to learn how to get the most of Eclipse Che:

• Customize Che workspaces for your projects
• Automatically run VSCode Extensions in Che workspaces
• Starting a workspace from a Git repository URL
• Making a workspace portable using a devfile
• Configure your instance of Che using the CheCluster Kubernetes Custom Resource
• Use and customize the embedded VSCode extensions registry.

Feedback and Community

We love to hear from users and developers. Here are the various ways to get in touch with us:

• Support: You can ask questions, report bugs, and request features using GitHub issues.
• Public Chat: Join the public eclipse-che Mattermost channel to discuss with community and contributors.
• Twitter: @eclipse_che
• Mailing List: [email protected]
• Weekly Meetings: Join us in our Che community meeting every second monday.

Contributing

If you are interested in fixing issues and contributing directly to the code base:

• 🐛 Submitting bugs
• 📄 Contributor license agreement
• 🏁 Development workflows
• 📝 Improve docs
• 🏗️ Che architecture
• Che repositories
• ✨ Good first issue for new contributors

Extending Eclipse Che

• Customize the default dev tooling container (the universal developer image or UDI).
• Customize the list of getting started samples.
• Add your own editor definition.

Roadmap

We maintain the Che roadmap in the open way. We welcome anyone to ask question and contribute to the roadmap by joining our community meetings.

License

Eclipse Public License 2.0.

che's Issues

Eclipse Che start error

my environment:
java -version
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)

JAVA_HOME is /usr/java/jdk1.8.0_66

the start error：

/opt/the/assembly-main/target/eclipse-che-4.0.0-beta-8-SNAPSHOT/eclipse-che-4.0.0-beta-8-SNAPSHOT/bin/che.sh start

!!! This Linux user is not in docker group. See https://docs.docker.com/engine/installation/ubuntulinux/#create-a-docker-group

Looks like something went wrong. Possible issues:

1. (Win | Mac) VirtualBox not installed ==> Rerun Docker Toolbox installation
2. (Win | Mac) Docker Machine not installed ==> Rerun Docker Toolbox installation
3. (Win | Mac) Docker is not reachable ==> Docker VM failed to start
4. (Win | Mac) Docker ok, but docker ps fails ==> Docker environment variables not set properly
5. (Linux) Docker is not reachable ==> Install: wget -qO- https://get.docker.com/ | sh
6. (Linux) Permissions not properly set ==> Che must run as UID 1000 with user in docker group
7. Could not find the Che app server ==> Did /tomcat get moved away from CHE_HOME?
8. Wrong version of Java found ==> Che requires Java 1.8
9. Did you use the right parameter syntax? ==> See usage

We have seen issues with VirtualBox on Windows where your VM gets corrupted when your computer is
suspended while the VM is still running. This will appear as SSH or ethernet connection issues. This is
rare, but if encountered, current known solution is to uninstall VirtualBox and Docker Toolbox, and then
reinstall.

Che Environment Variables:
(REQUIRED) JAVA_HOME ==> Location of Java runtime
(REQUIRED: WIN|MAC) DOCKER_TOOLBOX_INSTALL_PATH ==> Location of Docker Toolbox
(REQUIRED: WIN|MAC) VBOX_MSI_INSTALL_PATH ==> Location of VirtualBox
(OPTIONAL) CHE_HOME ==> Directory where Che is installed
(OPTIONAL) CHE_LOCAL_CONF_DIR ==> Directory with custom Che .properties files
(OPTIONAL) CHE_LOGS_DIR ==> Directory for Che output logs
(OPTIONAL) CHE_DOCKER_MACHINE_NAME ==> (Win | Mac) Name of VM created by docker-machine
(OPTIONAL) DOCKER_MACHINE_HOST ==> (Linux) Docker host IP - set if browser clients remote

Usage:
che [OPTIONS] [run | start | stop]
-i, --image Launches Che within a Docker container using latest image
-i:tag, --image:tag Launches Che within a Docker container using specific image tag
-p:port, --port:port Port that Che server will use for HTTP requests; default=8080
-r:ip, --remote:ip If Che clients are not localhost, set to IP address of Che server
-m:vm, --machine:vm For Win & Mac, sets the docker-machine VM name to vm; default=default
-s, --suppress Do not print browser client connection information
-h, --help Show this help
-d, --debug Use debug mode (prints command line options + app server debug)
run Starts Che application server in current console
start Starts Che application server in new console
stop Stops Che application server

The -r flag sets the DOCKER_MACHINE_HOST system environment variable. Set this to the IP address of the node
that is running your Docker daemon. Only necessary to set this if on Linux and your browser clients are not
localhost, ie they are remote. This property automatically set for Che on Windows and Mac.

!!! Could not find Docker client. Expected at Windows: %DOCKER_TOOLBOX_INSTALL_PATH%\docker.exe, Mac: /usr/local/bin/docker, Linux: /usr/bin/docker.

Looks like something went wrong. Possible issues:

1. (Win | Mac) VirtualBox not installed ==> Rerun Docker Toolbox installation
2. (Win | Mac) Docker Machine not installed ==> Rerun Docker Toolbox installation
3. (Win | Mac) Docker is not reachable ==> Docker VM failed to start
4. (Win | Mac) Docker ok, but docker ps fails ==> Docker environment variables not set properly
5. (Linux) Docker is not reachable ==> Install: wget -qO- https://get.docker.com/ | sh
6. (Linux) Permissions not properly set ==> Che must run as UID 1000 with user in docker group
7. Could not find the Che app server ==> Did /tomcat get moved away from CHE_HOME?
8. Wrong version of Java found ==> Che requires Java 1.8
9. Did you use the right parameter syntax? ==> See usage

We have seen issues with VirtualBox on Windows where your VM gets corrupted when your computer is
suspended while the VM is still running. This will appear as SSH or ethernet connection issues. This is
rare, but if encountered, current known solution is to uninstall VirtualBox and Docker Toolbox, and then
reinstall.

Che Environment Variables:
(REQUIRED) JAVA_HOME ==> Location of Java runtime
(REQUIRED: WIN|MAC) DOCKER_TOOLBOX_INSTALL_PATH ==> Location of Docker Toolbox
(REQUIRED: WIN|MAC) VBOX_MSI_INSTALL_PATH ==> Location of VirtualBox
(OPTIONAL) CHE_HOME ==> Directory where Che is installed
(OPTIONAL) CHE_LOCAL_CONF_DIR ==> Directory with custom Che .properties files
(OPTIONAL) CHE_LOGS_DIR ==> Directory for Che output logs
(OPTIONAL) CHE_DOCKER_MACHINE_NAME ==> (Win | Mac) Name of VM created by docker-machine
(OPTIONAL) DOCKER_MACHINE_HOST ==> (Linux) Docker host IP - set if browser clients remote

Usage:
che [OPTIONS] [run | start | stop]
-i, --image Launches Che within a Docker container using latest image
-i:tag, --image:tag Launches Che within a Docker container using specific image tag
-p:port, --port:port Port that Che server will use for HTTP requests; default=8080
-r:ip, --remote:ip If Che clients are not localhost, set to IP address of Che server
-m:vm, --machine:vm For Win & Mac, sets the docker-machine VM name to vm; default=default
-s, --suppress Do not print browser client connection information
-h, --help Show this help
-d, --debug Use debug mode (prints command line options + app server debug)
run Starts Che application server in current console
start Starts Che application server in new console
stop Stops Che application server

The -r flag sets the DOCKER_MACHINE_HOST system environment variable. Set this to the IP address of the node
that is running your Docker daemon. Only necessary to set this if on Linux and your browser clients are not
localhost, ie they are remote. This property automatically set for Che on Windows and Mac.

API for updating project files

I started a Che instance on my Mac. I am able to use IDE and all its basic features. However, I see that APIs exposed don't match with the documented ones. I couldn't find any API for updating project files. Endpoint mentioned in the docs also seems to be incorrect.

Output: http://localhost:8080/api
{"rootResources":[{"path":"project-template","regex":"/project-template(/.)?","fqn":"org.eclipse.che.api.project.server.ProjectTemplateService"},{"path":"event-bus","regex":"/event-bus(/.)?","fqn":"org.eclipse.che.api.core.notification.WSocketEventBusServer"},{"path":"/workspace","regex":"/workspace(/.)?","fqn":"org.eclipse.che.api.workspace.server.WorkspaceService"},{"path":"/machine","regex":"/machine(/.)?","fqn":"org.eclipse.che.api.machine.server.MachineService"},{"path":"/profile","regex":"/profile(/.)?","fqn":"org.eclipse.che.api.user.server.UserProfileService"},{"path":"/async/{ws-id}","regex":"/async/([^/]+?)(/.)?","fqn":"org.everrest.core.impl.async.AsynchronousJobService"},{"path":"/recipe","regex":"/recipe(/.)?","fqn":"org.eclipse.che.api.machine.server.recipe.RecipeService"},{"path":"oauth","regex":"/oauth(/.)?","fqn":"org.eclipse.che.security.oauth.OAuthAuthenticationService"},{"path":"/auth","regex":"/auth(/.)?","fqn":"org.eclipse.che.api.auth.AuthenticationService"},{"path":"/user","regex":"/user(/.)?","fqn":"org.eclipse.che.api.user.server.UserService"},{"path":"/ssh","regex":"/ssh(/.)?","fqn":"org.eclipse.che.api.ssh.server.SshService"},{"path":"/","regex":"(/.)?","fqn":"org.eclipse.che.api.core.rest.ApiInfoService"}]}

Is there any configuration to be enabled to get all APIs?

Why the exposed port range is 32768-65535, which is not the same as the range in che.properties?

In the Dockerfile:

# expose 8080 port and a range of ports for runners

EXPOSE 8080 32768-65535

But in /assembly-ide-war/src/main/webapp/WEB-INF/classes/codenvy/che.properties`

# range of available service ports
sys.resources.min_port=49152
sys.resources.max_port=65535

I wonder why the start port is different? And what's usage of the ports between 32768 and 49152?

Che server does not start

Downloaded che latest, unip and trying to launch using che.bat. It seems that startup script che.sh fails on the JDK version check (even though I have the required 1.8 version installed).

C:\Users\anbhatia\Documents\eclipse-che-latest\eclipse-che-4.0.0-beta-12\bin>che.bat

#############################################################
On Windows, Che projects can only reside in %userprofile% due
to limitations of Docker. On this computer, %userprofile% is
C:\Usersnbhatia
#############################################################

Docker machine named default already exists...
Setting environment variables for machine default...
Docker is configured to use vbox docker-machine named default with IP 192.168.99.100...

############## HOW TO CONNECT YOUR CHE CLIENT ###############
After Che server has booted, you can connect your clients by:
1. Open browser to http://localhost:8080, or:
2. Open native chromium app.
#############################################################

C:\Users\anbhatia\Documents\eclipse-che-latest\eclipse-che-4.0.0-beta-12\bin>

My environment - Win 7, JDK 1.8, Git 2.7.0:

C:\Users\anbhatia\Documents\eclipse-che-latest\eclipse-che-4.0.0-beta-12\bin>bash --version
GNU bash, version 4.3.42(5)-release (x86_64-pc-msys)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

C:\Users\anbhatia\Documents\eclipse-che-latest\eclipse-che-4.0.0-beta-12\bin>ver

Microsoft Windows [Version 6.1.7601]
C:\Users\anbhatia\Documents\eclipse-che-latest\eclipse-che-4.0.0-beta-12\bin>"%JAVA_HOME%"\bin\java -version
java version "1.8.0_72"
Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)

C:\Users\anbhatia\Documents\eclipse-che-latest\eclipse-che-4.0.0-beta-12\bin>

Incorrect error message che.sh

che/assembly-ide/src/assembly/bin/che.sh

line 236, 257

error_exit "!!! DOCKER_TOOL_BOX_INSTALL_PATH environment variable not set. Add it or rerun Docker Toolbox installation.!!!"

should be

error_exit "!!! DOCKER_TOOLBOX_INSTALL_PATH environment variable not set. Add it or rerun Docker Toolbox installation.!!!"

TOOLBOX is one word

127.0.0.1:8080 always redirects to /che/default for Chrome

I uninstalled Che, checked every autocomplete setting there is, and my browser is still redirecting me to /che/default/ whenever I visit 127.0.0.1 through Chrome. Doesn't do the same on Firefox. This is probably more of a Chrome bug but I thought I would report it here for any luck.

Can't start machine dev-machine. Connection timed out

I am trying to run che on an Amazon EC2 instance running Ubuntu 14.04 (also tried Amazon AMI) and have trouble creating workspaces. I get the following error:

2016-01-08 18:55:52,613[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 615] - Can't start machine dev-machine. Connection timed out
org.eclipse.che.api.machine.server.exception.MachineException: Can't start machine dev-machine. Connection timed out
at org.eclipse.che.api.machine.server.MachineManager.getRecipeByLocation(MachineManager.java:981) ~[che-core-api-machine-4.0.0-beta-5.jar:4.0.0-beta-5]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:292) ~[che-core-api-machine-4.0.0-beta-5.jar:4.0.0-beta-5]
...

Everything I'm doing so far seems pretty boilerplate. The one exception of course is that my client browser is remote. Same thing happens if I launch it in a docker container vs. locally. Any idea what I'm doing wrong?

How can I know if a file is in git index or not, from IDE?

I'm trying the git feature provided by che. But I have a problem that I can't figure out which of the files are in git index just from IDE.

You can see there are three files:

and they have the same icons.

I tried to click on the "status" option from "git" menu:

But it reports an error:

So I have to open the terminal tab, use git status command:

I wonder if we can know this information just from IDE and menus, without typing commands?

Folders that only contain one subfolder break the UI

I have imported a git project that contains nested folders with no content for several levels deep. Che seems to collapse these into one folder and breaks navigation.

If I go into the terminal and throw a dummy file into each folder touch .foo, the UI will work as expected.

Better DTO Generation

Hi,

In this thread I would like to address the architectural issues of the current approach for providing DTO functionality in Che.

The current approach relies on reflection which requires a fully compiled DTO definition interfaces before generating the DTO implementations. This forces Che extensions that generate DTOs to explicitly add sources re-compile during the maven build process in order to get consistent results. The result is a complex non-standard configuration and dependencies in pom.xml.

A better approach is using Java Annotation Processing which allows integrating into the compilation phase seamlessly with minimal configuration. APT also provides native methods for adding resources to the compilation, without any need for ad-hoc maven configurations.

Another major issue is the code generation method. Currently the DTO generation generates code by appending hundreds of string token. This is very hazardous and hard to maintain/develop. The standard way for code generation is using text templating engines such as StringTemplate or FreeMarker. Such tools allow defining the code templates externally and simplify the operation greatly.

I have a POC for a DTO processor that generates sever code. Many feature are already supported well and some tests with example use are included
https://github.com/tareqhs/che-core/tree/dto_processor
This change is required in the dependency mangement
https://github.com/tareqhs/che-depmgt/tree/st4_version

Please review my suggestion and provide any insights,
thank you

Where is the docker image for che 4.x?

I can only install che 3.x from docker:

docker pull codenvy/che

Is there one for 4.x?

Is it possible to run a single Java file or a Java test from the UI?

I installed the latest eclipse-che and created a simple maven java project. It contains a very simple Java application:

package maven_test;

/**
 * Hello world!
 *
 */
public class App 
{
    public static void main( String[] args )
    {
        System.out.println( "Hello World!" );
    }
}

And a test:

package maven_test;

import junit.framework.Test;
import junit.framework.TestCase;
import junit.framework.TestSuite;

/**
 * Unit test for simple App.
 */
public class AppTest 
    extends TestCase
{
    /**
     * Create the test case
     *
     * @param testName name of the test case
     */
    public AppTest( String testName )
    {
        super( testName );
    }

    /**
     * @return the suite of tests being tested
     */
    public static Test suite()
    {
        return new TestSuite( AppTest.class );
    }

    /**
     * Rigourous Test :-)
     */
    public void testApp()
    {
        assertTrue( true );
    }
}

I want to run the application or the test, and chose the Java 7 runner. It works, but finally gives me an error:

[DOCKER] Removing intermediate container 75ec0758cf27
[DOCKER] Successfully built ec65a2f775dc
[INFO] Environment preparation done. Application maven-test starting up…
[STDERR] no main manifest attribute, in application.jar
[INFO] Run ended @ Fri Dec 04 06:33:55 UTC 2015
[INFO] Application maven-test has been shutdown.

How to configure che to support running a specified Java file? Is there any plugin support it?

Can't find which port is using by tomcat for `codenvy/ubuntu_jdk8` (che 4.x)

My workspace is based on codenvy/ubuntu_jdk8, and I found it should bind to port 8080 for tomcat from the "Servers" tab:

If I docker exec -it <container_id> bash to corresponding container, I can see there is running the tomcat:

user@76ea98bc2d0f:/$ ps -eaf | grep tomcat
user        32     1  0 02:40 ?        00:00:18 /opt/jdk1.8.0_45/bin/java -Djava.util.logging.config.file=/home/user/che/ext-server/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms256m -Xmx1024m -server -Dche.logs.dir=/home/user/che/ext-server/logs -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dche.local.conf.dir=/mnt/che/conf -agentlib:jdwp=transport=dt_socket,address=4403,server=y,suspend=n -Djava.endorsed.dirs=/home/user/che/ext-server/endorsed -classpath /home/user/che/ext-server/conf/:/opt/jdk1.8.0_45/lib/tools.jar:/home/user/che/ext-server/bin/bootstrap.jar:/home/user/che/ext-server/bin/tomcat-juli.jar -Dcatalina.base=/home/user/che/ext-server -Dcatalina.home=/home/user/che/ext-server -Djava.io.tmpdir=/home/user/che/ext-server/temp org.apache.catalina.startup.Bootstrap start
user       236   213  0 03:39 ?        00:00:00 grep --color=auto tomcat

But the port 8080 is not used by anyone:

user@76ea98bc2d0f:/$ netstat -npl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:4403            0.0.0.0:*               LISTEN      32/java
tcp6       0      0 :::57273                :::*                    LISTEN      32/java
tcp6       0      0 :::4411                 :::*                    LISTEN      24/terminal
tcp6       0      0 :::32001                :::*                    LISTEN      32/java
tcp6       0      0 :::32101                :::*                    LISTEN      32/java
tcp6       0      0 :::4401                 :::*                    LISTEN      32/java
tcp6       0      0 127.0.0.1:4405          :::*                    LISTEN      32/java
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node   PID/Program name    Path
user@76ea98bc2d0f:/$

How can I find which port is really used by tomcat? And is there anything wrong?

About the feature of "remote machine"

Hi, when I'm reading the doc of Custom Machines, I found there is a feature of remote machine:

Environments contain one or more machines. A machine is an abstraction for a single run time, defined by a recipe or stack. A machine can have different implementations and our default implementation is to have one Docker container for each machine. Different Che deployments can have different implementations for machines such as localhost or a remote VM.

Any changes made to the project files within the machine is synchronized back to the workspace master out of the machine. On local systems this happens through a simple mount. On distributed systems, Che uses an rsync protocol to keep project files synchronized between machines and the workspace that owns the machine.

I'm quite interested in this feature, but can't find more information.

What is a remote VM? How can we create a remote VM? Is the remote VM is a docker container, or any other virtual hosts like digital ocean, aws ec2, or something?

For now, is this feature available that I can have a try myself?

Data is lost when I restart my che in docker, how to prevent it?

I install eclipse-che via docker, following this article: http://eclipse-che.readme.io/docs/install-using-docker, and I start che as:

docker run --privileged -it -p 8080:8080 -p 49152-49162:49152-49162 codenvy/che

The problem is when I restart my che, all data (including created projects/downloaded dependencies).

How to prevent it? If I need to mount something when I start the docker to store the data outside the docker, which directories do I need to care?

Build docker image failed

I tried to build the docker image:

cd che
docker build -t freewind/che:try1 .

But it fails:

Step 8 : ADD /assembly-ide/target/eclipse-che-*/eclipse-che-* /home/user/che
No source files were specified

Do I need to do something else before building? (e.g. mvn clean install)

Why will `che.sh` be invoked when the docker container is started?

This is might be a more "docker" question than "che".

I'm starting to read the code to resolve my problems, and when I see Dockerfile, I can't figure out why che will start when the docker container is started?

From the file: https://github.com/codenvy/che/blob/master/Dockerfile, I can't find where the che related shell is invoked:

FROM ubuntu
RUN apt-get update && apt-get -y install curl sudo procps wget && \
    echo "%sudo ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers && \
    useradd -u 1000 -G users,sudo -d /home/user --shell /bin/bash -m user && \
    echo "secret\nsecret" | passwd user && \
    curl -sSL https://get.docker.com/ | sh && \
    usermod -aG docker user && sudo apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

USER user
ENV JAVA_VERSION=8u65 \
    JAVA_VERSION_PREFIX=1.8.0_65 \
    CHE_LOCAL_CONF_DIR=/home/user/.che
RUN mkdir /home/user/.che && \
    wget \
   --no-cookies \
   --no-check-certificate \
   --header "Cookie: oraclelicense=accept-securebackup-cookie" \
   -qO- \
   "http://download.oracle.com/otn-pub/java/jdk/$JAVA_VERSION-b17/jre-$JAVA_VERSION-linux-x64.tar.gz" | sudo tar -zx -C /opt/
ENV JAVA_HOME /opt/jre$JAVA_VERSION_PREFIX

# expose 8080 port and a range of ports for runners

EXPOSE 8080 32768-65535

ADD /assembly-main/target/eclipse-che-*/eclipse-che-* /home/user/che

CMD  sudo chown -R user:user /home/user/che && \
     sudo service docker start && tail -f /dev/null

Thanks for help~

My che container starts very slow

From @eivantsov's video of starting che container in a digital ocean server, it just uses less than 3 minutes in total (including downloading che images, creating workspace, until it's ready):

https://www.youtube.com/watch?v=UVucYKI5NHs

But for me, most time of the it's pretty slow. The fastest record is about 10 minutes, and most of the time, it needs me 20 minutes or so to do the same thing as in eivantsov's video. And the longest record is 60 minutes (starting che container: 41minutes, other things 20 minutes)

So I wonder what's your configurations in your digital ocean? Mine is:

• 4GB Ram
• 60GB SSD Disk
• San Francisco

Require password

I use docker to install Che, but access it does not require a password, how to enter the password when access?

`docker ps` checking fails randomly

I found it quite often to view following information when running che in docker, like docker run -it --rm --privileged nowind/academy-che:2016-01-09-9e4369517e4308593fce0895d4700e77ecba12f8-x bash -c " sudo service docker start && cd /home/user/che/bin/ && ./che.sh -r:159.203.211.163 run", which is running on digital ocean.

 * Starting Docker: docker                                               [ OK ]

!!! Running 'docker' succeeded, but 'docker ps' failed. This usually means that docker cannot reach its daemon.

Looks like something went wrong. Possible issues:
  1. (Win | Mac) VirtualBox not installed          ==> Rerun Docker Toolbox installation
  2. (Win | Mac) Docker Machine not installed      ==> Rerun Docker Toolbox installation
  3. (Win | Mac) Docker is not reachable           ==> Docker VM failed to start
  4. (Win | Mac) Docker ok, but docker ps fails    ==> Docker environment variables not set properly
  5. (Linux) Docker is not reachable               ==> Install: wget -qO- https://get.docker.com/ | sh
  6. Could not find the Che app server             ==> Did /tomcat get moved away from CHE_HOME?
  7. Did you use the right parameter syntax?       ==> See usage

We have seen issues with VirtualBox on windows where your VM gets corrupted when your computer is suspended while the VM is still running. This will appear as SSH or ethernet connection issues. This is rare, but if encountered, current known solution is to uninstall VirtualBox and Docker Toolbox, and then reinstall.

Che Environment Variables:
  (REQUIRED) JAVA_HOME                             ==> Location of Java runtime
  (REQUIRED: WIN|MAC) DOCKER_TOOLBOX_INSTALL_PATH  ==> Location of Docker Toolbox
  (REQUIRED: WIN|MAC) VBOX_MSI_INSTALL_PATH        ==> Location of VirtualBox
  (OPTIONAL) CHE_HOME                              ==> Directory where Che is installed
  (OPTIONAL) CHE_LOCAL_CONF_DIR                    ==> Directory with custom Che .properties files
  (OPTIONAL) CHE_LOGS_DIR                          ==> Directory for Che output logs


Usage:
  che [-i] [-i:tag] [-p:port] [-r:ip] [-m:vm] [-d] [run | start | stop]

     -i,      --image        Launches Che within a Docker container using latest image
     -i:tag,  --image:tag    Launches Che within a Docker container using specific image tag
     -p:port, --port:port    Port that Che server will use for HTTP requests; default=8080
     -r:ip,   --remote:ip    If Che clients are not localhost, set to IP address of Che server
     -m:vm,   --machine:vm   For Win & Mac, sets the docker-machine VM name to vm; default=default
     -s,      --suppress     Do not print browser client connection information
     -h,      --help         Show this help
     -d,      --debug        Use debug mode (prints command line options + app server debug)
     run                     Starts Che application server in current console
     start                   Starts Che application server in new console
     stop                    Stops Che application server

The -r flag sets the DOCKER_MACHINE_HOST system environment variable. Set this to the IP address of the node
that is running your Docker daemon. Only necessary to set this if on Linux and your browser clients are not
localhost, ie they are remote. This property automatically set for Che on Windows and Mac.

The long docker image nowind/academy-che:2016-01-09-9e4369517e4308593fce0895d4700e77ecba12f8-x is my own-made images. The only difference between my image and the official one is the Dockerfile. I removed the invocation of che.sh, and it becomes in my Dockerfile:

RUN sudo chown -R user:user /home/user/che && \
    sudo service docker start

To fix this, I have to sudo reboot my server, and it will work OK with the same command.

---

Although I have it today with my own image, but I had the same problem these days with official images, and "reboot" is the only way to fix it.

Not sure if you have the same issue? If not, just keep it here, and I will update if I have any news

compile error

git log
commit d2ab49a
Merge: 2815a83 1a5ee0d
Author: Alexander Garagatyi [email protected]
Date: Fri Dec 25 16:37:40 2015 +0200

Merge pull request #141 from codenvy/IDEX-3726

IDEX-3726: adopt ws agent to run it as common machine process

[INFO] --- maven-compiler-plugin:3.3:compile (default-compile) @ assembly-ide-war ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 5 source files to /home/wu560130911/projects/che/assembly-ide-war/target/classes
warning: Supported source version 'RELEASE_6' from annotation processor 'org.jvnet.hudson.annotation_indexer.AnnotationProcessorImpl' less than -source '1.7'
/home/wu560130911/projects/che/assembly-ide-war/src/main/java/org/eclipse/che/api/deploy/ApiModule.java:116: error: cannot find symbol
bindConstant().annotatedWith(Names.named(DockerMachineExtServerLauncher.WS_AGENT_PROCESS_START_COMMAND))
^
symbol: variable WS_AGENT_PROCESS_START_COMMAND
location: class DockerMachineExtServerLauncher
1 error
1 warning

depency problem

$ mvn clean install
[INFO] Scanning for projects...
Downloading: http://192.168.11.201:8081/nexus/content/groups/public/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-M5-SNAPSHOT/maven-metadata.xml
Downloading: http://192.168.11.201:8081/nexus/content/groups/public/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-M5-SNAPSHOT/maven-depmgt-pom-4.0.0-M5-SNAPSHOT.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.eclipse.che.sdk:che-sdk-parent:4.0.0-M5-SNAPSHOT: Could not find artifact org.eclipse.che.depmgt:maven-depmgt-pom:pom:4.0.0-M5-SNAPSHOT in nexus-osc (http://192.168.11.201:8081/nexus/content/groups/public) and 'parent.relativePath' points at wrong local POM @ org.eclipse.che.sdk:che-sdk-parent:4.0.0-M5-SNAPSHOT, D:\develop\che\pom.xml, line 16, column 13
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.eclipse.che.sdk:assembly-sdk:unknown-version has 1 error
[ERROR] Non-resolvable parent POM for org.eclipse.che.sdk:che-sdk-parent:4.0.0-M5-SNAPSHOT: Could not find artifact org.eclipse.che.depmgt:maven-depmgt-pom:pom:4.0.0-M5-SNAPSHOT in nexus-osc (http://192.168.11.201:8081/nexus/content/groups/public) and 'parent.relativePath' points at wrong local POM @ org.eclipse.che.sdk:che-sdk-parent:4.0.0-M5-SNAPSHOT, D:\develop\che\pom.xml, line 16, column 13 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

404 after install

After installing and running in the browser address on port 8080. In response comes a 404 error.

OS: CentOS 6.7
JDK: 1.8.0

When you start seeing errors:

2015-12-07 15:08:39,838[ost-startStop-1]  [INFO ] [com.google.inject.Guice 42]          - An exception was caught and reported. Message: org.eclipse.che.inject.ConfigurationException: Property HOSTNAME%%.* is not found as system property or environment variable.
org.eclipse.che.inject.ConfigurationException: Property HOSTNAME%%.* is not found as system property or environment variable.
    at org.eclipse.che.inject.CheBootstrap$AbstractConfigurationModule.bindProperties(CheBootstrap.java:243) ~[che-core-commons-inject-4.0.0-M5-SNAPSHOT.jar:4.0.0-M5-SNAPSHOT]
    at org.eclipse.che.inject.CheBootstrap$AbstractConfigurationModule.bindProperties(CheBootstrap.java:214) ~[che-core-commons-inject-4.0.0-M5-SNAPSHOT.jar:4.0.0-M5-SNAPSHOT]
    at org.eclipse.che.inject.CheBootstrap$ExtConfiguration.configure(CheBootstrap.java:160) ~[che-core-commons-inject-4.0.0-M5-SNAPSHOT.jar:4.0.0-M5-SNAPSHOT]
    at com.google.inject.AbstractModule.configure(AbstractModule.java:62) ~[guice-4.0.jar:na]
    at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340) ~[guice-4.0.jar:na]
    at com.google.inject.spi.Elements.getElements(Elements.java:110) ~[guice-4.0.jar:na]
    at com.google.inject.util.Modules$OverrideModule.configure(Modules.java:198) ~[guice-4.0.jar:na]
    at com.google.inject.AbstractModule.configure(AbstractModule.java:62) ~[guice-4.0.jar:na]
    at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340) ~[guice-4.0.jar:na]
    at com.google.inject.spi.Elements.getElements(Elements.java:110) ~[guice-4.0.jar:na]
    at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138) ~[guice-4.0.jar:na]
    at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) [guice-4.0.jar:na]
    at com.google.inject.Guice.createInjector(Guice.java:96) [guice-4.0.jar:na]
    at org.everrest.guice.servlet.EverrestGuiceContextListener.getInjector(EverrestGuiceContextListener.java:137) [everrest-integration-guice-1.10.0.jar:na]
    at com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47) [guice-servlet-4.0.jar:na]
    at org.everrest.guice.servlet.EverrestGuiceContextListener.contextInitialized(EverrestGuiceContextListener.java:84) [everrest-integration-guice-1.10.0.jar:na]
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4738) [catalina.jar:8.0.28]
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5181) [catalina.jar:8.0.28]
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:8.0.28]
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725) [catalina.jar:8.0.28]
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701) [catalina.jar:8.0.28]
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717) [catalina.jar:8.0.28]
    at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:945) [catalina.jar:8.0.28]
    at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1798) [catalina.jar:8.0.28]
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [na:1.8.0_60]
    at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.8.0_60]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.8.0_60]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.8.0_60]
    at java.lang.Thread.run(Unknown Source) [na:1.8.0_60]
2015-12-07 15:08:40,557[ost-startStop-1]  [ERROR] [o.a.c.c.C.[.[localhost].[/che] 4744] - Exception sending context initialized event to listener instance of class org.eclipse.che.inject.CodenvyBootstrap
com.google.inject.CreationException: Unable to create injector, see the following errors:

1) An exception was caught and reported. Message: Property HOSTNAME%%.* is not found as system property or environment variable.
  at com.google.inject.util.Modules$OverrideModule.configure(Modules.java:198)

1 error
    at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466) ~[guice-4.0.jar:na]
    at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155) ~[guice-4.0.jar:na]
    at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) ~[guice-4.0.jar:na]
    at com.google.inject.Guice.createInjector(Guice.java:96) ~[guice-4.0.jar:na]
    at org.everrest.guice.servlet.EverrestGuiceContextListener.getInjector(EverrestGuiceContextListener.java:137) ~[everrest-integration-guice-1.10.0.jar:na]
    at com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47) ~[guice-servlet-4.0.jar:na]
    at org.everrest.guice.servlet.EverrestGuiceContextListener.contextInitialized(EverrestGuiceContextListener.java:84) ~[everrest-integration-guice-1.10.0.jar:na]
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4738) [catalina.jar:8.0.28]
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5181) [catalina.jar:8.0.28]
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:8.0.28]
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725) [catalina.jar:8.0.28]
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701) [catalina.jar:8.0.28]
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717) [catalina.jar:8.0.28]
    at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:945) [catalina.jar:8.0.28]
    at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1798) [catalina.jar:8.0.28]
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [na:1.8.0_60]
    at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.8.0_60]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.8.0_60]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.8.0_60]
    at java.lang.Thread.run(Unknown Source) [na:1.8.0_60]
Caused by: org.eclipse.che.inject.ConfigurationException: Property HOSTNAME%%.* is not found as system property or environment variable.
    at org.eclipse.che.inject.CheBootstrap$AbstractConfigurationModule.bindProperties(CheBootstrap.java:243) ~[che-core-commons-inject-4.0.0-M5-SNAPSHOT.jar:4.0.0-M5-SNAPSHOT]
    at org.eclipse.che.inject.CheBootstrap$AbstractConfigurationModule.bindProperties(CheBootstrap.java:214) ~[che-core-commons-inject-4.0.0-M5-SNAPSHOT.jar:4.0.0-M5-SNAPSHOT]
    at org.eclipse.che.inject.CheBootstrap$ExtConfiguration.configure(CheBootstrap.java:160) ~[che-core-commons-inject-4.0.0-M5-SNAPSHOT.jar:4.0.0-M5-SNAPSHOT]
    at com.google.inject.AbstractModule.configure(AbstractModule.java:62) ~[guice-4.0.jar:na]
    at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340) ~[guice-4.0.jar:na]
    at com.google.inject.spi.Elements.getElements(Elements.java:110) ~[guice-4.0.jar:na]
    at com.google.inject.util.Modules$OverrideModule.configure(Modules.java:198) ~[guice-4.0.jar:na]
    at com.google.inject.AbstractModule.configure(AbstractModule.java:62) ~[guice-4.0.jar:na]
    at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340) ~[guice-4.0.jar:na]
    at com.google.inject.spi.Elements.getElements(Elements.java:110) ~[guice-4.0.jar:na]
    at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138) ~[guice-4.0.jar:na]
    at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) ~[guice-4.0.jar:na]
    ... 17 common frames omitted
2015-12-07 15:08:40,943[ost-startStop-1]  [ERROR] [o.a.c.core.StandardContext 5182]     - One or more listeners failed to start. Full details will be found in the appropriate container log file
2015-12-07 15:08:41,861[ost-startStop-1]  [INFO ] [o.a.c.u.SessionIdGeneratorBase 241]  - Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [914] milliseconds.
2015-12-07 15:08:41,862[ost-startStop-1]  [ERROR] [o.a.c.core.StandardContext 5233]     - Context [/che] startup failed due to previous errors
2015-12-07 15:08:41,880[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 980]        - Deployment of web application archive /home/che/assembly-sdk/target/assembly-sdk-4.0.0-M5-SNAPSHOT/assembly-sdk-4.0.0-M5-SNAPSHOT/webapps/che.war has finished in 8,899 ms
2015-12-07 15:08:41,881[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 916]        - Deploying web application archive /home/che/assembly-sdk/target/assembly-sdk-4.0.0-M5-SNAPSHOT/assembly-sdk-4.0.0-M5-SNAPSHOT/webapps/dashboard.war
2015-12-07 15:08:41,964[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 980]        - Deployment of web application archive /home/che/assembly-sdk/target/assembly-sdk-4.0.0-M5-SNAPSHOT/assembly-sdk-4.0.0-M5-SNAPSHOT/webapps/dashboard.war has finished in 83 ms
2015-12-07 15:08:41,965[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 1036]       - Deploying web application directory /home/che/assembly-sdk/target/assembly-sdk-4.0.0-M5-SNAPSHOT/assembly-sdk-4.0.0-M5-SNAPSHOT/webapps/ROOT
2015-12-07 15:08:42,028[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 1152]       - Deployment of web application directory /home/che/assembly-sdk/target/assembly-sdk-4.0.0-M5-SNAPSHOT/assembly-sdk-4.0.0-M5-SNAPSHOT/webapps/ROOT has finished in 63 ms
2015-12-07 15:08:42,037[main]             [INFO ] [o.a.c.http11.Http11NioProtocol 469]  - Starting ProtocolHandler ["http-nio-8080"]
2015-12-07 15:08:42,046[main]             [INFO ] [o.a.catalina.startup.Catalina 638]   - Server startup in 9483 ms

How to pass config when starting a machine?

In 4.x, when creating a workspace, we can select an image like UBUNTU_JDK8.

Since in China, it's quite slow to visit maven repository sometimes, so I want to bind the local ~/.m2 directory to the docker containers to reuse them jars across multi containers.

But I can't find a way to add such config, how to do it?

How to uninstall?

How can I uninstall che on OSX environment completely. It messed up my docker configurations.

Debuggin in che

Hi,

I wanted to see how debugging works when developing extensions. I followed this guide to get che running locally and it seems to work fine when I go to localhost:8080. I used the Spring sample project, but when I hit Run > Debug an error pops up saying:

500 Internal Server Error http://localhost:8080/che/api/debug-java/1q2w3e/connect

And no debugging view shows up and I can't set breakpoints, as is the case when I run the same sample project at codenvy.com.

This is the stack trace I'm getting:

HTTP Status 500 - java.lang.NoClassDefFoundError: com/sun/jdi/connect/IllegalConnectorArgumentsException

type Exception report

message java.lang.NoClassDefFoundError: com/sun/jdi/connect/IllegalConnectorArgumentsException

description The server encountered an internal error that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: java.lang.NoClassDefFoundError: com/sun/jdi/connect/IllegalConnectorArgumentsException
    org.everrest.core.servlet.EverrestServlet.service(EverrestServlet.java:76)
    org.eclipse.che.api.local.CheGuiceEverrestServlet.service(CheGuiceEverrestServlet.java:36)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
    com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
    com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
    com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
    com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
    org.eclipse.che.env.local.server.SingleEnvironmentFilter.doFilter(SingleEnvironmentFilter.java:95)
    com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
    com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
    com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
    com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
    com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
root cause

java.lang.NoClassDefFoundError: com/sun/jdi/connect/IllegalConnectorArgumentsException
    org.eclipse.che.ide.ext.java.jdi.server.DebuggerService.create(DebuggerService.java:44)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.lang.reflect.Method.invoke(Method.java:497)
    org.everrest.core.impl.method.DefaultMethodInvoker.invokeMethod(DefaultMethodInvoker.java:154)
    org.everrest.core.impl.method.DefaultMethodInvoker.invokeMethod(DefaultMethodInvoker.java:141)
    org.everrest.core.impl.RequestDispatcher.doInvokeResource(RequestDispatcher.java:289)
    org.everrest.core.impl.RequestDispatcher.invokeSubResourceMethod(RequestDispatcher.java:280)
    org.everrest.core.impl.RequestDispatcher.dispatch(RequestDispatcher.java:205)
    org.everrest.core.impl.RequestDispatcher.dispatch(RequestDispatcher.java:95)
    org.everrest.core.impl.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:64)
    org.everrest.core.impl.EverrestProcessor.process(EverrestProcessor.java:134)
    org.everrest.core.servlet.EverrestServlet.service(EverrestServlet.java:63)
    org.eclipse.che.api.local.CheGuiceEverrestServlet.service(CheGuiceEverrestServlet.java:36)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
    com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
    com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
    com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
    com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
    org.eclipse.che.env.local.server.SingleEnvironmentFilter.doFilter(SingleEnvironmentFilter.java:95)
    com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
    com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
    com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
    com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
    com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
root cause

java.lang.ClassNotFoundException: com.sun.jdi.connect.IllegalConnectorArgumentsException
    org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1305)
    org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1157)
    org.eclipse.che.ide.ext.java.jdi.server.DebuggerService.create(DebuggerService.java:44)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.lang.reflect.Method.invoke(Method.java:497)
    org.everrest.core.impl.method.DefaultMethodInvoker.invokeMethod(DefaultMethodInvoker.java:154)
    org.everrest.core.impl.method.DefaultMethodInvoker.invokeMethod(DefaultMethodInvoker.java:141)
    org.everrest.core.impl.RequestDispatcher.doInvokeResource(RequestDispatcher.java:289)
    org.everrest.core.impl.RequestDispatcher.invokeSubResourceMethod(RequestDispatcher.java:280)
    org.everrest.core.impl.RequestDispatcher.dispatch(RequestDispatcher.java:205)
    org.everrest.core.impl.RequestDispatcher.dispatch(RequestDispatcher.java:95)
    org.everrest.core.impl.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:64)
    org.everrest.core.impl.EverrestProcessor.process(EverrestProcessor.java:134)
    org.everrest.core.servlet.EverrestServlet.service(EverrestServlet.java:63)
    org.eclipse.che.api.local.CheGuiceEverrestServlet.service(CheGuiceEverrestServlet.java:36)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
    com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
    com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
    com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
    com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
    org.eclipse.che.env.local.server.SingleEnvironmentFilter.doFilter(SingleEnvironmentFilter.java:95)
    com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
    com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
    com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
    com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
    com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
note The full stack trace of the root cause is available in the Apache Tomcat/8.0.21 logs.

Apache Tomcat/8.0.21

Is this an actual bug or am I missing something?

Custom image fails on workspace build, stuck in "Starting"

When creating a workspace based on an image that fails to execute/build/etc it gets stuck in "Starting" state. When there it can't be deleted, stopped, recovered, etc - or at least I haven't been able to find a way to yet.

连接过多

编译安装eclipse-che-4.0.0-M6-SNAPSHOT，启动后，socket连接迅速涨到10万个，第一次请求后，tomcat报错
2015-12-25 16:32:12,226[main] [ERROR] [o.a.c.core.StandardServer 464] - StandardServer.await: accept:
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.socketAccept(Native Method) ~[na:1.8.0_65]
at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) ~[na:1.8.0_65]
at java.net.ServerSocket.implAccept(ServerSocket.java:545) ~[na:1.8.0_65]
at java.net.ServerSocket.accept(ServerSocket.java:513) ~[na:1.8.0_65]
at org.apache.catalina.core.StandardServer.await(StandardServer.java:446) ~[catalina.jar:8.0.28]
at org.apache.catalina.startup.Catalina.await(Catalina.java:713) [catalina.jar:8.0.28]
at org.apache.catalina.startup.Catalina.start(Catalina.java:659) [catalina.jar:8.0.28]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_65]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_65]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_65]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_65]
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351) [bootstrap.jar:8.0.28]
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485) [bootstrap.jar:8.0.28]

README.md - Link to Write Che IDE Plug-Ins broken

Link to Write Che IDE Plug-Ins (https://eclipse-che.readme.io/docs/extension-development-workflow) broken on README.md, showing a 404 error. What's the correct link?

How can I provide custom che properties outside the docker?

I install eclipse-che via docker, I want to provide custom properties from outside docker, which file do I need to mount?

I see there is /home/user/che-3.13.4.2/webapps/che/WEB-INF/classes/codenvy/che.properties inside the docker, is it correct file I need to mount with?

Where can I find the git hash from a che docker image?

When I use the latest codenvy/che:nightly, I found there is something wrong (not sure if it's code issues or just my wrong usage), but I have already tagged a previous good image as a backup.

Now I want to see what't the git hash of the code in that docker image, so I can checkout the code and do something, but not sure how to do it. Is there any file recorded the git hash in the image? Or is there any other way I can find it?

How to hide the projects belong to other workspaces?

Finally, I got eclipse-che 4.x running, and created several different workspace, and created different projects in some of them:

But the problem is, when I open the lipeng3 workspace http://localhost:8080/che/lipeng3, it will also show the test_another_spring project which belongs to another workspace

I can even edit it:

Since I want to create workspaces for different users, they should not see other's projects. Is there any way to hide them?

Incorrect buld & run instructions on http://eclipse.org/che

Currenly mainpage of the progect says:

# <...>
git clone https://github.com/codenvy/che 
git checkout 4.0 
cd assembly-sdk
mvn clean install

cd ..
./che run
http://localhost:8080

These script doesnt work for 4.0 at least

1. (minor) add "cd ./che" after clonning
2. there is no che.bat/che.sh neither in root nor assembly-sdk
   Please, update the mainpage

Docs may out of date

I followed the docs on documentation , after git checkout openshift and execute mvn clean install, I got these errors:

[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.eclipse.che.depmgt:maven-depmgt-pom:4.0.0-M5 (/root/che-depmgt/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not transfer artifact org.eclipse.che.parent:maven-parent-pom:pom:4.0.0-M5 from/to codenvy-public-repo (https://maven.codenvycorp.com/content/groups/public/): maven.codenvycorp.com: unknown error and 'parent.relativePath' points at no local POM @ line 16, column 13: Unknown host maven.codenvycorp.com: unknown error -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

actually these two urls are not reachable:

Downloading: https://maven.codenvycorp.com/content/repositories/codenvy-public-snapshots/org/eclipse/che/parent/maven-parent-pom/4.0.0-M5/maven-parent-pom-4.0.0-M5.pom
Downloading: https://repo.maven.apache.org/maven2/org/eclipse/che/parent/maven-parent-pom/4.0.0-M5/maven-parent-pom-4.0.0-M5.pom

Too many open files with `codenvy/che:nightly`

I have the same problem with this issue #140.

I run the image codenvy/che:nightly in a virtual box, which is running ubuntu 14.04, and the "open files" settings is increased as following:

scaleworks@ubuntu:~$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 31375
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 100000
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 200000
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

and append the following to /etc/security/limits.conf:

*                hard    nofile          100000
*                hard    nproc           200000
*                soft    nofile          100000
*                soft    nproc           200000

Then I start codenvy/che:nightly:

$ docker run -it -p 8080:8080 codenvy/che:nightly

It seems started correctly:

$ docker run -it -p 8080:8080 codenvy/che:nightly
 * Starting Docker: docker                                               [ OK ]
Using CATALINA_BASE:   /home/user/che/tomcat
Using CATALINA_HOME:   /home/user/che/tomcat
Using CATALINA_TMPDIR: /home/user/che/tomcat/temp
Using JRE_HOME:        /opt/jre1.8.0_65
Using CLASSPATH:       /home/user/che/tomcat/conf/:/opt/jre1.8.0_65/lib/tools.jar:/home/user/che/tomcat/bin/bootstrap.jar:/home/user/che/tomcat/bin/tomcat-juli.jar
2015-12-29 06:10:51,681[main]             [INFO ] [o.a.c.s.VersionLoggerListener 89]    - Server version:        Apache Tomcat/8.0.28
2015-12-29 06:10:51,683[main]             [INFO ] [o.a.c.s.VersionLoggerListener 91]    - Server built:          Oct 7 2015 18:25:21 UTC
2015-12-29 06:10:51,683[main]             [INFO ] [o.a.c.s.VersionLoggerListener 93]    - Server number:         8.0.28.0
2015-12-29 06:10:51,683[main]             [INFO ] [o.a.c.s.VersionLoggerListener 95]    - OS Name:               Linux
2015-12-29 06:10:51,684[main]             [INFO ] [o.a.c.s.VersionLoggerListener 97]    - OS Version:            3.13.0-32-generic
2015-12-29 06:10:51,684[main]             [INFO ] [o.a.c.s.VersionLoggerListener 99]    - Architecture:          amd64
2015-12-29 06:10:51,684[main]             [INFO ] [o.a.c.s.VersionLoggerListener 101]   - Java Home:             /opt/jre1.8.0_65
2015-12-29 06:10:51,684[main]             [INFO ] [o.a.c.s.VersionLoggerListener 103]   - JVM Version:           1.8.0_65-b17
2015-12-29 06:10:51,685[main]             [INFO ] [o.a.c.s.VersionLoggerListener 105]   - JVM Vendor:            Oracle Corporation
2015-12-29 06:10:51,685[main]             [INFO ] [o.a.c.s.VersionLoggerListener 107]   - CATALINA_BASE:         /home/user/che/tomcat
2015-12-29 06:10:51,685[main]             [INFO ] [o.a.c.s.VersionLoggerListener 109]   - CATALINA_HOME:         /home/user/che/tomcat
2015-12-29 06:10:51,685[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Djava.util.logging.config.file=/home/user/che/tomcat/conf/logging.properties
2015-12-29 06:10:51,686[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
2015-12-29 06:10:51,687[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Xms256m
2015-12-29 06:10:51,688[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Xmx1024m
2015-12-29 06:10:51,688[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Dche.logs.dir=/home/user/che/tomcat/logs/
2015-12-29 06:10:51,688[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Dcom.sun.management.jmxremote
2015-12-29 06:10:51,689[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Dcom.sun.management.jmxremote.ssl=false
2015-12-29 06:10:51,689[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Dcom.sun.management.jmxremote.authenticate=false
2015-12-29 06:10:51,690[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Dche.local.conf.dir=/home/user/.che
2015-12-29 06:10:51,690[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Dche.home=/home/user/che
2015-12-29 06:10:51,690[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Djava.endorsed.dirs=/home/user/che/tomcat/endorsed
2015-12-29 06:10:51,690[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Dcatalina.base=/home/user/che/tomcat
2015-12-29 06:10:51,690[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Dcatalina.home=/home/user/che/tomcat
2015-12-29 06:10:51,691[main]             [INFO ] [o.a.c.s.VersionLoggerListener 115]   - Command line argument: -Djava.io.tmpdir=/home/user/che/tomcat/temp
2015-12-29 06:10:51,826[main]             [INFO ] [o.a.c.http11.Http11NioProtocol 424]  - Initializing ProtocolHandler ["http-nio-8080"]
2015-12-29 06:10:51,835[main]             [INFO ] [o.a.t.util.net.NioSelectorPool 72]   - Using a shared selector for servlet write/read
2015-12-29 06:10:51,837[main]             [INFO ] [o.a.catalina.startup.Catalina 587]   - Initialization processed in 416 ms
2015-12-29 06:10:51,854[main]             [INFO ] [c.m.JmxRemoteLifecycleListener 332]  - The JMX Remote Listener has configured the registry on port 32001 and the server on port 32101 for the Platform server
2015-12-29 06:10:51,854[main]             [INFO ] [o.a.c.core.StandardService 433]      - Starting service Catalina
2015-12-29 06:10:51,854[main]             [INFO ] [o.a.c.core.StandardEngine 259]       - Starting Servlet Engine: Apache Tomcat/8.0.28
2015-12-29 06:10:51,910[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 916]        - Deploying web application archive /home/user/che/tomcat/webapps/che.war
2015-12-29 06:10:56,477[ost-startStop-1]  [INFO ] [.c.p.d.c.DockerRegistryChecker 43]   - Probing registry 'http://localhost:5000'
2015-12-29 06:10:56,487[ost-startStop-1]  [WARN ] [.c.p.d.c.DockerRegistryChecker 50]   - Docker registry http://localhost:5000 is not available, which means that you won't be able to save snapshots of your workspaces.
How to configure registry?
    Local registry  -> https://docs.docker.com/registry/
    Remote registry -> set up 'docker.registry.auth.*' properties
2015-12-29 06:10:58,125[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 980]        - Deployment of web application archive /home/user/che/tomcat/webapps/che.war has finished in 6,215 ms
2015-12-29 06:10:58,131[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 916]        - Deploying web application archive /home/user/che/tomcat/webapps/dashboard.war
2015-12-29 06:10:58,305[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 980]        - Deployment of web application archive /home/user/che/tomcat/webapps/dashboard.war has finished in 174 ms
2015-12-29 06:10:58,307[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 1036]       - Deploying web application directory /home/user/che/tomcat/webapps/ROOT
2015-12-29 06:10:58,386[ost-startStop-1]  [INFO ] [o.a.c.startup.HostConfig 1152]       - Deployment of web application directory /home/user/che/tomcat/webapps/ROOT has finished in 79 ms
2015-12-29 06:10:58,394[main]             [INFO ] [o.a.c.http11.Http11NioProtocol 469]  - Starting ProtocolHandler ["http-nio-8080"]
2015-12-29 06:10:58,401[main]             [INFO ] [o.a.catalina.startup.Catalina 638]   - Server startup in 6562 ms

But now I can't run any commands, even the simplest ls:

$ ls
-bash: start_pipeline: pgrp pipe: Too many open files in system
-bash: /bin/ls: Too many open files in system

Then I visit the che from browser:

http://10.202.128.49:8080/

It doesn't show anything, instead, I can see many "Too many open files in system" showing on the log:

2015-12-29 06:10:58,401[main]             [INFO ] [o.a.catalina.startup.Catalina 638]   - Server startup in 6562 ms

2015-12-29 06:11:26,236[8080-Acceptor-0]  [ERROR] [o.a.t.util.net.NioEndpoint 709]      - Socket accept failed
java.io.IOException: Too many open files in system
    at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) ~[na:1.8.0_65]
    at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422) ~[na:1.8.0_65]
    at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250) ~[na:1.8.0_65]
    at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:682) ~[tomcat-coyote.jar:8.0.28]
    at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
2015-12-29 06:11:26,289[8080-Acceptor-0]  [ERROR] [o.a.t.util.net.NioEndpoint 709]      - Socket accept failed
java.io.IOException: Too many open files in system
    at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) ~[na:1.8.0_65]
    at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422) ~[na:1.8.0_65]
    at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250) ~[na:1.8.0_65]
    at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:682) ~[tomcat-coyote.jar:8.0.28]
    at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
2015-12-29 06:11:26,392[8080-Acceptor-0]  [ERROR] [o.a.t.util.net.NioEndpoint 709]      - Socket accept failed
java.io.IOException: Too many open files in system
    at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) ~[na:1.8.0_65]
    at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422) ~[na:1.8.0_65]
    at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250) ~[na:1.8.0_65]
    at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:682) ~[tomcat-coyote.jar:8.0.28]
    at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]

I tried to docker ps but failed:

-bash: start_pipeline: pgrp pipe: Too many open files in system
-bash: /usr/bin/docker: Too many open files in system

Can't connect to ws://che-host:8080 when creating new project

I started a new che by docker run -it --privileged -p 8080:8080 codenvy/che:nightly, then open the dashboard: http://myip:8080/dashboard, and create the first project.

But it fails:

The error information is:

[STDOUT] 2016-01-01 03:21:42,614[rrest.WSClient8] [INFO ] [.c.a.c.n.WSocketEventBusClient 223] - Open connection to ws://che-host:8080/che/api/eventbus/?token=dummy_token.
[STDOUT] 2016-01-01 03:21:44,608[ventBusClient-0] [WARN ] [.c.a.c.n.WSocketEventBusClient 256] - Not able to connect to ws://che-host:8080/che/api/eventbus/?token=dummy_token because Connection timeout. Retrying

User management

How to manage registered users and allow each of them have their own projects?

I'm going to set a che on a server, and allow the students of the class have their own workspace and own projects. But I found for a che instance, there is only one shared workspace and not support for user registering or custom workspace.

Build error

I want to build,but get error!
my environment:
java -version
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)

mvn clean -X
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T00:41:47+08:00)
Maven home: /opt/apache-maven-3.3.9
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: /usr/java/jdk1.8.0_66/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-431.el6.x86_64", arch: "amd64", family: "unix"
[DEBUG] Created new class realm maven.api
[DEBUG] Importing foreign packages into class realm maven.api
[DEBUG] Imported: javax.enterprise.inject.* < plexus.core
[DEBUG] Imported: javax.enterprise.util.* < plexus.core
[DEBUG] Imported: javax.inject.* < plexus.core
[DEBUG] Imported: org.apache.maven.* < plexus.core
[DEBUG] Imported: org.apache.maven.artifact < plexus.core
[DEBUG] Imported: org.apache.maven.classrealm < plexus.core
[DEBUG] Imported: org.apache.maven.cli < plexus.core
[DEBUG] Imported: org.apache.maven.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.exception < plexus.core
[DEBUG] Imported: org.apache.maven.execution < plexus.core
[DEBUG] Imported: org.apache.maven.execution.scope < plexus.core
[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core
[DEBUG] Imported: org.apache.maven.model < plexus.core
[DEBUG] Imported: org.apache.maven.monitor < plexus.core
[DEBUG] Imported: org.apache.maven.plugin < plexus.core
[DEBUG] Imported: org.apache.maven.profiles < plexus.core
[DEBUG] Imported: org.apache.maven.project < plexus.core
[DEBUG] Imported: org.apache.maven.reporting < plexus.core
[DEBUG] Imported: org.apache.maven.repository < plexus.core
[DEBUG] Imported: org.apache.maven.rtinfo < plexus.core
[DEBUG] Imported: org.apache.maven.settings < plexus.core
[DEBUG] Imported: org.apache.maven.toolchain < plexus.core
[DEBUG] Imported: org.apache.maven.usability < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.* < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.events < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core
[DEBUG] Imported: org.codehaus.classworlds < plexus.core
[DEBUG] Imported: org.codehaus.plexus.* < plexus.core
[DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core
[DEBUG] Imported: org.codehaus.plexus.component < plexus.core
[DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core
[DEBUG] Imported: org.codehaus.plexus.container < plexus.core
[DEBUG] Imported: org.codehaus.plexus.context < plexus.core
[DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core
[DEBUG] Imported: org.codehaus.plexus.logging < plexus.core
[DEBUG] Imported: org.codehaus.plexus.personality < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core
[DEBUG] Imported: org.eclipse.aether.* < plexus.core
[DEBUG] Imported: org.eclipse.aether.artifact < plexus.core
[DEBUG] Imported: org.eclipse.aether.collection < plexus.core
[DEBUG] Imported: org.eclipse.aether.deployment < plexus.core
[DEBUG] Imported: org.eclipse.aether.graph < plexus.core
[DEBUG] Imported: org.eclipse.aether.impl < plexus.core
[DEBUG] Imported: org.eclipse.aether.installation < plexus.core
[DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core
[DEBUG] Imported: org.eclipse.aether.metadata < plexus.core
[DEBUG] Imported: org.eclipse.aether.repository < plexus.core
[DEBUG] Imported: org.eclipse.aether.resolution < plexus.core
[DEBUG] Imported: org.eclipse.aether.spi < plexus.core
[DEBUG] Imported: org.eclipse.aether.transfer < plexus.core
[DEBUG] Imported: org.eclipse.aether.version < plexus.core
[DEBUG] Imported: org.slf4j.* < plexus.core
[DEBUG] Imported: org.slf4j.helpers.* < plexus.core
[DEBUG] Imported: org.slf4j.spi.* < plexus.core
[DEBUG] Populating class realm maven.api
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from /opt/apache-maven-3.3.9/conf/settings.xml
[DEBUG] Reading user settings from /root/.m2/settings.xml
[DEBUG] Reading global toolchains from /opt/apache-maven-3.3.9/conf/toolchains.xml
[DEBUG] Reading user toolchains from /root/.m2/toolchains.xml
[DEBUG] Using local repository at /root/.m2/repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for /root/.m2/repository
[INFO] Scanning for projects...
[DEBUG] Could not find metadata org.eclipse.che.depmgt:maven-depmgt-pom:4.0.0-beta-8-SNAPSHOT/maven-metadata.xml in local (/root/.m2/repository)
[DEBUG] Using transporter WagonTransporter with priority -1.0 for https://maven.codenvycorp.com/content/groups/public/
[DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://maven.codenvycorp.com/content/groups/public/
[DEBUG] Using transporter WagonTransporter with priority -1.0 for https://maven.codenvycorp.com/content/repositories/codenvy-public-snapshots/
[DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://maven.codenvycorp.com/content/repositories/codenvy-public-snapshots/
Downloading: https://maven.codenvycorp.com/content/groups/public/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-beta-8-SNAPSHOT/maven-metadata.xml
Downloading: https://maven.codenvycorp.com/content/repositories/codenvy-public-snapshots/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-beta-8-SNAPSHOT/maven-metadata.xml
[DEBUG] Writing tracking file /root/.m2/repository/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-beta-8-SNAPSHOT/resolver-status.properties
[DEBUG] Writing tracking file /root/.m2/repository/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-beta-8-SNAPSHOT/resolver-status.properties
[WARNING] Could not transfer metadata org.eclipse.che.depmgt:maven-depmgt-pom:4.0.0-beta-8-SNAPSHOT/maven-metadata.xml from/to codenvy-public-repo (https://maven.codenvycorp.com/content/groups/public/): maven.codenvycorp.com: unknown error
org.eclipse.aether.transfer.MetadataTransferException: Could not transfer metadata org.eclipse.che.depmgt:maven-depmgt-pom:4.0.0-beta-8-SNAPSHOT/maven-metadata.xml from/to codenvy-public-repo (https://maven.codenvycorp.com/content/groups/public/): maven.codenvycorp.com: unknown error
at org.eclipse.aether.connector.basic.MetadataTransportListener.transferFailed(MetadataTransportListener.java:43)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:222)
at org.eclipse.aether.internal.impl.DefaultMetadataResolver$ResolveTask.run(DefaultMetadataResolver.java:607)
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.maven.wagon.TransferFailedException: maven.codenvycorp.com: unknown error
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1066)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:960)
at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at org.eclipse.aether.transport.wagon.WagonTransporter$GetTaskRunner.run(WagonTransporter.java:560)
at org.eclipse.aether.transport.wagon.WagonTransporter.execute(WagonTransporter.java:427)
at org.eclipse.aether.transport.wagon.WagonTransporter.get(WagonTransporter.java:404)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:447)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)
... 8 more
Caused by: java.net.UnknownHostException: maven.codenvycorp.com: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:101)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.maven.wagon.providers.http.httpclient.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.maven.wagon.providers.http.httpclient.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:832)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:983)
... 17 more
[WARNING] Could not transfer metadata org.eclipse.che.depmgt:maven-depmgt-pom:4.0.0-beta-8-SNAPSHOT/maven-metadata.xml from/to codenvy-public-snapshots-repo (https://maven.codenvycorp.com/content/repositories/codenvy-public-snapshots/): maven.codenvycorp.com
org.eclipse.aether.transfer.MetadataTransferException: Could not transfer metadata org.eclipse.che.depmgt:maven-depmgt-pom:4.0.0-beta-8-SNAPSHOT/maven-metadata.xml from/to codenvy-public-snapshots-repo (https://maven.codenvycorp.com/content/repositories/codenvy-public-snapshots/): maven.codenvycorp.com
at org.eclipse.aether.connector.basic.MetadataTransportListener.transferFailed(MetadataTransportListener.java:43)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:222)
at org.eclipse.aether.internal.impl.DefaultMetadataResolver$ResolveTask.run(DefaultMetadataResolver.java:607)
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.maven.wagon.TransferFailedException: maven.codenvycorp.com
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1066)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:960)
at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at org.eclipse.aether.transport.wagon.WagonTransporter$GetTaskRunner.run(WagonTransporter.java:560)
at org.eclipse.aether.transport.wagon.WagonTransporter.execute(WagonTransporter.java:427)
at org.eclipse.aether.transport.wagon.WagonTransporter.get(WagonTransporter.java:404)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:447)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)
... 8 more
Caused by: java.net.UnknownHostException: maven.codenvycorp.com
at java.net.InetAddress.getAllByName0(InetAddress.java:1280)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:101)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.maven.wagon.providers.http.httpclient.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.maven.wagon.providers.http.httpclient.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:832)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:983)
... 17 more
[DEBUG] Using transporter WagonTransporter with priority -1.0 for https://maven.codenvycorp.com/content/groups/public/
[DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://maven.codenvycorp.com/content/groups/public/
Downloading: https://maven.codenvycorp.com/content/groups/public/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-beta-8-SNAPSHOT/maven-depmgt-pom-4.0.0-beta-8-SNAPSHOT.pom
[DEBUG] Writing tracking file /root/.m2/repository/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-beta-8-SNAPSHOT/maven-depmgt-pom-4.0.0-beta-8-SNAPSHOT.pom.lastUpdated
[DEBUG] Using transporter WagonTransporter with priority -1.0 for https://maven.codenvycorp.com/content/repositories/codenvy-public-snapshots/
[DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://maven.codenvycorp.com/content/repositories/codenvy-public-snapshots/
Downloading: https://maven.codenvycorp.com/content/repositories/codenvy-public-snapshots/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-beta-8-SNAPSHOT/maven-depmgt-pom-4.0.0-beta-8-SNAPSHOT.pom
[DEBUG] Writing tracking file /root/.m2/repository/org/eclipse/che/depmgt/maven-depmgt-pom/4.0.0-beta-8-SNAPSHOT/maven-depmgt-pom-4.0.0-beta-8-SNAPSHOT.pom.lastUpdated
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.eclipse.che:che-parent:4.0.0-beta-8-SNAPSHOT: Could not transfer artifact org.eclipse.che.depmgt:maven-depmgt-pom:pom:4.0.0-beta-8-SNAPSHOT from/to codenvy-public-repo (https://maven.codenvycorp.com/content/groups/public/): maven.codenvycorp.com and 'parent.relativePath' points at wrong local POM @ line 16, column 13
@
[ERROR] The build could not read 1 project -> [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.eclipse.che:che-parent:4.0.0-beta-8-SNAPSHOT: Could not transfer artifact org.eclipse.che.depmgt:maven-depmgt-pom:pom:4.0.0-beta-8-SNAPSHOT from/to codenvy-public-repo (https://maven.codenvycorp.com/content/groups/public/): maven.codenvycorp.com and 'parent.relativePath' points at wrong local POM @ line 16, column 13

    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:422)
    at org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:419)
    at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:410)
    at org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:83)
    at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:491)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:219)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

[ERROR]
[ERROR] The project org.eclipse.che:che-parent:4.0.0-beta-8-SNAPSHOT (/opt/WYY/che/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for org.eclipse.che:che-parent:4.0.0-beta-8-SNAPSHOT: Could not transfer artifact org.eclipse.che.depmgt:maven-depmgt-pom:pom:4.0.0-beta-8-SNAPSHOT from/to codenvy-public-repo (https://maven.codenvycorp.com/content/groups/public/): maven.codenvycorp.com and 'parent.relativePath' points at wrong local POM @ line 16, column 13: Unknown host maven.codenvycorp.com -> [Help 2]
org.apache.maven.model.resolution.UnresolvableModelException: Could not transfer artifact org.eclipse.che.depmgt:maven-depmgt-pom:pom:4.0.0-beta-8-SNAPSHOT from/to codenvy-public-repo (https://maven.codenvycorp.com/content/groups/public/): maven.codenvycorp.com
at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:197)
at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:246)
at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:1000)
at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:800)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:329)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:469)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:438)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:401)
at org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:419)
at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:410)
at org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:83)
at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:491)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:219)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.eclipse.che.depmgt:maven-depmgt-pom:pom:4.0.0-beta-8-SNAPSHOT from/to codenvy-public-repo (https://maven.codenvycorp.com/content/groups/public/): maven.codenvycorp.com
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)
at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:193)
... 25 more
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.eclipse.che.depmgt:maven-depmgt-pom:pom:4.0.0-beta-8-SNAPSHOT from/to codenvy-public-repo (https://maven.codenvycorp.com/content/groups/public/): maven.codenvycorp.com
at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:43)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
... 29 more
Caused by: org.apache.maven.wagon.TransferFailedException: maven.codenvycorp.com
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1066)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:960)
at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at org.eclipse.aether.transport.wagon.WagonTransporter$GetTaskRunner.run(WagonTransporter.java:560)
at org.eclipse.aether.transport.wagon.WagonTransporter.execute(WagonTransporter.java:427)
at org.eclipse.aether.transport.wagon.WagonTransporter.get(WagonTransporter.java:404)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:447)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)
... 34 more
Caused by: java.net.UnknownHostException: maven.codenvycorp.com
at java.net.InetAddress.getAllByName0(InetAddress.java:1280)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:101)
at org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.maven.wagon.providers.http.httpclient.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.maven.wagon.providers.http.httpclient.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:832)
at org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:983)
... 43 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

How to create a html+js project in 4.x

With the built-in "ubuntu_jdk8" or "debian_jdk8", I can create Java projects successfully. But how can I create a normal html+js project?

I can create a blank project and create some html/js files, but not sure how to run the machine to give me a url to visit.

I also tried to create a new workspace based on FROM codenvy/javascript_html, but I can't create any project in this workspace, there is no template, and the "Create" button is always disabled:

---

Along with this question, I also want to know how to create a nodejs project

Is it possible to start many che instances on a server?

Since we didn't find the way to allow users to have their custom workspace, I want to start many che instances on a server, so everyone can get its own che instance to set its own workspace.

But I have a problem that the server has only 4G ram, and there are more than 20 students. If I install che on the server directly, the memory is not enough if I start many che, since to start a tomcat, it requires at least 512M(or more).

Can I resolve this problem by starting the che from docker containers? Is the memory used by docker container dynamic and shared? (Since most of the time the users are just typing code, the real used memory should be less then 4G)

Could you give me some advices on this, or any solution that users can have their custom workspaces?

Can't access web interface for docker image

Latest docker, Windows 7, following the docs at https://eclipse-che.readme.io/docs/install-using-docker.

After running the image, I can't connect to localhost:8080, or any other mapped port. I suspect it relates to these errors!

Oliver@velocity MINGW64 ~
$ docker run -it -p 9000:8080 -p 49152-49162:49152-49162 codenvy/che
Using CATALINA_BASE:   /home/user/che-3.13.4.2
Using CATALINA_HOME:   /home/user/che-3.13.4.2
Using CATALINA_TMPDIR: /home/user/che-3.13.4.2/temp
Using JRE_HOME:        /opt/jdk1.8.0_45
Using CLASSPATH:       /home/user/che-3.13.4.2/conf/:/opt/jdk1.8.0_45/lib/tools.jar:/home/user/che-3.13.4.2/bin/bootstrap.jar:/home/user/che-3.13.4.2/bin/tomcat-juli.jar
/dev/mapper/control: open failed: Operation not permitted
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Command failed
mount: permission denied
Could not mount /sys/kernel/security.
AppArmor detection and --privileged mode might break.
time="2015-12-02T22:01:47.227010437Z" level=error msg="'overlay' is not supported over aufs."
time="2015-12-02T22:01:47.310522402Z" level=fatal msg="Error starting daemon: Error initializing network controller: error obtaining controller instance: Failed to create NAT chain: iptables failed: iptables -t nat -N DOCKER: iptables v1.4.21: can't initialize iptables table `nat': Permission denied (you must be root)\nPerhaps iptables or your kernel needs to be upgraded.\n (exit status 3)"
2015-12-02 22:01:48,577[main]             [INFO ] [o.a.c.s.VersionLoggerListener 89]    - Server version:        Apache Tomcat/8.0.21
# Continues Tomcat launch

Oliver@velocity MINGW64 ~
$ docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      windows/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      linux/amd64

Compiling GWT Application Failed

mvn clean install

[INFO] ------------------------------------------------------------------------
[INFO] Building Che :: Compiling GWT Application 3.14.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://repo.jenkins-ci.org/public/org/jenkins-ci/jenkins/1.26/jenkins-1.26.pom
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Che :: Parent ...................................... SUCCESS [  3.370 s]
[INFO] Che :: Plugin Tools ................................ SUCCESS [  0.112 s]
[INFO] Che :: Plugin Tools :: API Plugin .................. SUCCESS [ 29.734 s]
[INFO] Che :: Examples .................................... SUCCESS [  2.262 s]
[INFO] Che :: Examples :: Action .......................... SUCCESS [  7.182 s]
[INFO] Che :: Examples :: Project Type .................... SUCCESS [  4.739 s]
[INFO] Che :: Examples :: Service ......................... SUCCESS [  3.938 s]
[INFO] Che :: Examples :: Theme ........................... SUCCESS [  5.742 s]
[INFO] Che :: Examples :: Multi Extension ................. SUCCESS [  0.068 s]
[INFO] Che :: Examples :: Multi Extension :: Action ....... SUCCESS [  4.514 s]
[INFO] Che :: Examples :: Multi Extension :: ProjectType .. SUCCESS [  4.425 s]
[INFO] Che :: Examples :: Multi Extension :: Service ...... SUCCESS [  3.818 s]
[INFO] Che :: Examples :: Multi Extension :: Theme ........ SUCCESS [  4.663 s]
[INFO] Che :: Examples :: Multi Extension :: Assembly ..... SUCCESS [  0.706 s]
[INFO] Che :: Archetypes .................................. SUCCESS [  0.159 s]
[INFO] Che :: Archetypes :: Client Extension .............. SUCCESS [  2.388 s]
[INFO] Che :: Archetypes :: Server Extension .............. SUCCESS [  0.089 s]
[INFO] Che :: Archetypes :: Project Type .................. SUCCESS [  0.113 s]
[INFO] Che :: Archetypes :: Multi module Extension ........ SUCCESS [  0.165 s]
[INFO] Che :: Admin war ................................... SUCCESS [  5.902 s]
[INFO] Che :: Compiling GWT Application ................... FAILURE [ 25.886 s]
[INFO] Che :: Assemblies Tomcat ........................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:51 min
[INFO] Finished at: 2015-12-09T11:56:39+08:00
[INFO] Final Memory: 135M/1175M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project assembly-sdk-war: Could not resolve dependencies for project org.eclipse.che.ide:assembly-sdk-war:war:3.14.0-SNAPSHOT: Failed to collect dependencies at org.eclipse.che.plugin:che-plugin-github-ext-github:jar:3.14.0-SNAPSHOT -> org.kohsuke:github-api:jar:1.67 -> com.infradna.tool:bridge-method-annotation:jar:1.14 -> org.jenkins-ci:annotation-indexer:jar:1.4: Failed to read artifact descriptor for org.jenkins-ci:annotation-indexer:jar:1.4: Could not transfer artifact org.jenkins-ci:jenkins:pom:1.26 from/to repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/): repo.jenkins-ci.org: unknown error: Unknown host repo.jenkins-ci.org: unknown error -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :assembly-sdk-war

What does "Project git url" be used?

In the "git" menu of a project, there is a "Project git url":

If I click on it, it will show a dialog with a local project url:

I tried to visit it from browser or git clone it, neither works. Just be curious what is that?

How to delete a running workspace?

I want to delete a running workspace, but show this error:

Failed! Can't remove running workspace workspace50isjk211hvsadni

How can I do it?

dashboard in docker

dashboard is not available (che in docker).
get 404.

https required

Exception in thread "DockerInstanceStopDetector-0" java.lang.IllegalArgumentException: Certificates are required for https connection.
at org.eclipse.che.plugin.docker.client.connection.TcpConnection.(TcpConnection.java:41)
at org.eclipse.che.plugin.docker.client.connection.DockerConnectionFactory.openConnection(DockerConnectionFactory.java:52)
at org.eclipse.che.plugin.docker.client.DockerConnector.getEvents(DockerConnector.java:766)
at org.eclipse.che.plugin.docker.machine.DockerInstanceStopDetector.lambda$detectContainersEvents$2(DockerInstanceStopDetector.java:107)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Start Che Error

i user centos 7,and docker -v:Docker version 1.9.1, build a34a1d5.
when i run:
docker run -it -p 8080:8080 -p 49152-49162:49152-49162 codenvy/che

who can help me?

----------Get this error:--------
mount: permission denied
rmdir: failed to remove 'cpu': Read-only file system
mount: permission denied
rmdir: failed to remove 'cpuacct': Read-only file system

• Starting Docker: docker [ OK ]

!!! Running 'docker' succeeded, but 'docker ps' failed. This usually means that docker cannot reach its daemon.

Looks like something went wrong. Possible issues:

1. (Win | Mac) VirtualBox not installed ==> Rerun Docker Toolbox installation
2. (Win | Mac) Docker Machine not installed ==> Rerun Docker Toolbox installation
3. (Win | Mac) Docker is not reachable ==> Docker VM failed to start
4. (Win | Mac) Docker ok, but docker ps fails ==> Docker environment variables not set properly
5. (Linux) Docker is not reachable ==> Install: wget -qO- https://get.docker.com/ | sh
6. (Linux) Permissions not properly set ==> Che must run as UID 1000 with user in docker group
7. Could not find the Che app server ==> Did /tomcat get moved away from CHE_HOME?
8. Wrong version of Java found ==> Che requires Java 1.8
9. Did you use the right parameter syntax? ==> See usage

We have seen issues with VirtualBox on Windows where your VM gets corrupted when your computer is
suspended while the VM is still running. This will appear as SSH or ethernet connection issues. This is
rare, but if encountered, current known solution is to uninstall VirtualBox and Docker Toolbox, and then
reinstall.

Che Environment Variables:
(REQUIRED) JAVA_HOME ==> Location of Java runtime
(REQUIRED: WIN|MAC) DOCKER_TOOLBOX_INSTALL_PATH ==> Location of Docker Toolbox
(REQUIRED: WIN|MAC) VBOX_MSI_INSTALL_PATH ==> Location of VirtualBox
(OPTIONAL) CHE_HOME ==> Directory where Che is installed
(OPTIONAL) CHE_LOCAL_CONF_DIR ==> Directory with custom Che .properties files
(OPTIONAL) CHE_LOGS_DIR ==> Directory for Che output logs
(OPTIONAL) CHE_DOCKER_MACHINE_NAME ==> (Win | Mac) Name of VM created by docker-machine
(OPTIONAL) DOCKER_MACHINE_HOST ==> (Linux) Docker host IP - set if browser clients remote

Usage:
che [OPTIONS] [run | start | stop]
-i, --image Launches Che within a Docker container using latest image
-i:tag, --image:tag Launches Che within a Docker container using specific image tag
-p:port, --port:port Port that Che server will use for HTTP requests; default=8080
-r:ip, --remote:ip If Che clients are not localhost, set to IP address of Che server
-m:vm, --machine:vm For Win & Mac, sets the docker-machine VM name to vm; default=default
-s, --suppress Do not print browser client connection information
-h, --help Show this help
-d, --debug Use debug mode (prints command line options + app server debug)
run Starts Che application server in current console
start Starts Che application server in new console
stop Stops Che application server

The -r flag sets the DOCKER_MACHINE_HOST system environment variable. Set this to the IP address of the node
that is running your Docker daemon. Only necessary to set this if on Linux and your browser clients are not
localhost, ie they are remote. This property automatically set for Che on Windows and Mac.

Can't create maven command with the name "newMaven"

It's a strange issue, when the name if "newMaven", it can't be created. The "Save" button is disabled.

There is no other existing task has the same name.

PS: Base on the commit 9e4369517e4308593fce0895d4700e77ecba12f8

How to use the provided tomcat8 in workspace image "codenvy/ubuntu_jdk8"?

I see in the provided "codenvy/ubuntu_jdk8", it has provided a tomcat8, and also exposes the port 8080.

But I'm not sure how to use it, do I have to start it manually? Or do I have to modify pom.xml and use it from some maven plugins?

Is there any example for a web application?

Passing argument to docker image

Latest docker image can start, but I hope I can pass some argument to the internal che.sh, like:

docker run --privileged -it --name che --net=host codenvy/che:nightly -r:111.111.111.111

I've tried but make it myself, but not successful. So I asked a question on stackoverflow: http://stackoverflow.com/questions/34691752/how-to-write-a-dockerfile-which-i-can-start-a-service-and-run-a-shell-and-also-a

Thanks for help