Error starting workspace, WorkspaceManager error

[boban74]

_1 Upvote_ Hi,

currently I am trying to get Eclipse Che running on Ubuntu 16.04 but with no luck. Starting an Workspace in Che ends up in a exception

2016-03-18 13:04:34,490[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 610] - Failed writing 8192 bytes org.eclipse.che.api.machine.server.exception.MachineException: Failed writing 8192 bytes at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:396) ~[che-core-api-machine-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:333) ~[che-core-api-machine-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:167) ~[che-core-api-machine-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:421) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:320) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:146) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:637) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:608) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.0.0-RC11.jar:4.0.0-RC11] ...

This is not the full stack trace but I think it is a Docker issue. Also trying to start Eclipse Che docker image ends up with an error. The image is downloaded but start fails with

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

If I run docker ps with -a option manually the container is listed but is not in running status. I have no idea ... i try a lot. User I am starting Eclipse Che is in docker group. Also testing Docker with a ubuntu image works well also the network in container is working ...

Linux Kernel 4.4
Eclipse Che 4RC11
Docker 1.10.2
Java 1.8.0_74
Maven 3.3.9
FS btrfs

Best regards
Boban

[pavan5000]

i had a same problem in Windows. i suspected that, this could be because of port conflicts. I restated my PC. It resolved it.

[boban74]

Hi pavan5000,

I don't think it is port conflict and in meantime I have already restarted my workstation ... no change

Thank you for the fast response,
Regards Boban

[ghost]

@boban74 can you provide the full stracktrace plase?

As to running in Docker, make sure /var/run/docker.sock has read/write permissions for a group.

[boban74]

Hi eivantsov,

here is the full stack trace running Eclipse Che and starting a workspace ...

016-03-18 20:26:07,156[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 610] - Failed writing 8192 bytes org.eclipse.che.api.machine.server.exception.MachineException: Failed writing 8192 bytes at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:396) ~[che-core-api-machine-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:333) ~[che-core-api-machine-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:167) ~[che-core-api-machine-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:421) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:320) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:146) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:637) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:608) ~[che-core-api-workspace-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-4.0.0-RC11.jar:4.0.0-RC11] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_74] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_74] at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_74] Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Failed writing 8192 bytes at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.buildImage(DockerInstanceProvider.java:318) ~[che-plugin-docker-machine-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.plugin.docker.machine.local.interceptor.EnableOfflineDockerMachineBuildInterceptor.invoke(EnableOfflineDockerMachineBuildInterceptor.java:58) ~[che-plugin-docker-machine-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:222) ~[che-plugin-docker-machine-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:356) ~[che-core-api-machine-4.0.0-RC11.jar:4.0.0-RC11] ... 11 common frames omitted Caused by: java.io.IOException: Failed writing 8192 bytes at org.eclipse.che.plugin.docker.client.connection.UnixSocketOutputStream.write(UnixSocketOutputStream.java:50) ~[che-plugin-docker-client-4.0.0-RC11.jar:4.0.0-RC11] at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) ~[na:1.8.0_74] at java.io.BufferedOutputStream.write(BufferedOutputStream.java:126) ~[na:1.8.0_74] at com.google.common.io.ByteStreams.copy(ByteStreams.java:74) ~[guava-18.0.jar:na] at org.eclipse.che.plugin.docker.client.connection.DockerConnection$StreamEntity.writeTo(DockerConnection.java:114) ~[che-plugin-docker-client-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.plugin.docker.client.connection.UnixSocketConnection.request(UnixSocketConnection.java:53) ~[che-plugin-docker-client-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.plugin.docker.client.connection.DockerConnection.request(DockerConnection.java:85) ~[che-plugin-docker-client-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.plugin.docker.client.DockerConnector.doBuildImage(DockerConnector.java:844) ~[che-plugin-docker-client-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.plugin.docker.client.DockerConnector.buildImage(DockerConnector.java:213) ~[che-plugin-docker-client-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.buildImage(DockerInstanceProvider.java:310) ~[che-plugin-docker-machine-4.0.0-RC11.jar:4.0.0-RC11] ... 14 common frames omitted

The group has read/write permissions on /var/run/docker.sock ... the user I'm starting the Eclipse Che belongs to group docker and docker group has the required permissions

Thank you for investigating sour time on my issue ...

Regards
Boban

[ghost]

Try enabling read/write for others (/var/run/docker.sock)

Another problem is that docker client and server versions vary in the container and on your host. However, this is very unlikely

[boban74]

Hi again,

I've changed the permission so the others have read/write access to /var/run/docker.sock ... no change. Where did yo see that the docker client and server vary?

Thanks again,
regards Boban

[ghost]

I just assumed that they may vary

You can try it this way https://eclipse-che.readme.io/docs/usage-docker#using-docker-syntax

Just make sure you add your own CMD which is bash

This way you get a shell into the container, and run docker ps there. The error message will say it all.

[boban74]

Hi Eugene,

I've run the codenvy/che image with

docker run -ti codenvy/che:latest /bin/bash

and there I run docker ps and get the error message

Cannot connect to the Docker daemon. Is the docker daemon running on this host?

running docker --version in codenvy/che container outputs Docker version 1.9.1, build a34a1d5 ... on my host is version 1.10.2 running. Your guess was right :). Is there a codenvy/che image with docker 1.10 or have i to downgrade to Docker version 1.9.1?

Thanks a lot, regards
Boban

[ghost]

It looks like different Docker versions isn't what causes the problem. I have just tried it on my local Ubuntu and works, although my docker version locally is 1.10.3 and it's 1.9.1 in the container.

I suspect that it's still a permissions issue with /var/run/docker.sock

[boban74]

Hi Eugene,

just tried it again ... the same error message already posted in previous comment ... this are my permissions ...
srw-rw-rw- 1 root docker 0 Mär 19 17:58 docker.sock
I start eclipse che desktop version 4RC11 with ./che.sh run without any error message. Then -> Workspaces -> + (create workspace). I choose java ready-to-go-stack, give it a name and press create. The creation of workspace works ...
2016-03-19 18:09:27,356[nio-8080-exec-2] [INFO ] [o.e.c.a.w.s.WorkspaceManager 140] - EVENT#workspace-created# WS#aaaaa# WS-ID#workspacenrg9mcdhd58h0dhc# USER#che#
On pressing run the just created workspace i get the error message. Stacktrace is above in previous post.

Thanks again,
Boban

[ghost]

As to the error when running Che natively, can you follow these instructions? #736 (comment)

As to running it in Docker, my docker.sock on Ubuntu 14.04 has the following permissions and ownership:

srw-rw---- 1 root docker 0 Mar 19 17:54 /var/run/docker.sock

Maybe it is Ubuntu 16 specific issue. Can you run id for a current user? What's docker GID on your system?

Do you have a chance to try the same on a different machine or VM?

Also, docker run -ti codenvy/che:latest /bin/bash was the wrong way to go, since you need to mount docker.socket -v /var/run/docker.sock:/var/run/docker.sock. When in a container, run docker ps.

[boban74]

Hi Eugene,

id outputs ...
uid=1000(boban) gid=1000(boban) Gruppen=1000(boban),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare),129(docker)
Dockers GID is 129 ...

Running docker ps in container with
docker run -v /var/run/docker.sock:/var/run/docker.sock -ti codenvy/che:latest /bin/bash
outputs the same error message
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

The logs, after changing the log level to SEVERE, are full of ...
016-03-20 09:19:25,663[eStopDetector-0] [DEBUG] [d.m.DockerInstanceStopDetector 113] - Error response from docker API, status: 400, message: 400 Bad Request: missing required Host header org.eclipse.che.plugin.docker.client.DockerException: Error response from docker API, status: 400, message: 400 Bad Request: missing required Host header at org.eclipse.che.plugin.docker.client.DockerConnector.getDockerException(DockerConnector.java:1180) ~[che-plugin-docker-client-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.plugin.docker.client.DockerConnector.getEvents(DockerConnector.java:764) ~[che-plugin-docker-client-4.0.0-RC11.jar:4.0.0-RC11] at org.eclipse.che.plugin.docker.machine.DockerInstanceStopDetector.lambda$detectContainersEvents$0(DockerInstanceStopDetector.java:107) ~[che-plugin-docker-machine-4.0.0-RC11.jar:4.0.0-RC11] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_74] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_74] at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_74]

I already tried it with ubuntu 15.10 and docker 1.6 ... there eclipse che is running without error ... Later i will update to docker 1.10 and test it again.

Regards
Boban

[ghost]

Can you attach the entire log file for me to take a look?

[boban74]

Hi Eugene,

just tested native eclipse che on ubuntu 15.10 with docker 1.10.3 and it works without errors ... as you said, maybe it is Ubuntu 16 specific issue ... I will attach entire logs later ---

My Ubuntu 16 workstation is installed on btrfs file system, could this make problems?

Regards,
Boban

[JAZ-013]

I think it is definitely leaning toward Ubuntu 16 being the issue. I'm getting these exact same symptoms while trying to get Che up and running for the first time. My versions are identical to @boban74 as far as I can tell.

[JAZ-013]

Some random info. The 'docker ps failed' message seems to come from inside the container? (is that a thing, I don't know docker). Not sure if this means anything but...

I added a 'set -x' to the bin/che.sh file and ran bin/che.sh -i. It stopped at /usr/bin/docker exec che bash -c '//home/user/che/bin/che.sh -p:8080 --skip:client run' which is where the error is output.

I'm then able to run /usr/bin/docker exec che bash -c '//home/user/che/bin/che.sh -p:8080 --skip:client run' which just gives me the last part of the error.

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

Usage:
che [OPTIONS] [COMMAND]
-m:name, --machine:name For Win & Mac, sets the docker-machine VM name; default=default
-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
-h, --help Show this help
-d, --debug Use debug mode (prints command line options + app server debug)

Options when running Che natively:
-b, --blocking-entropy Security: https://wiki.apache.org/tomcat/HowTo/FasterStartUp
-g, --registry Launch Docker registry as a container (used for ws snapshots)
-s:client, --skip:client Do not print browser client connection information
-s:java, --skip:java Do not enforce Java version checks
-s:uid, --skip:uid Do not enforce UID=1000 for Docker

Options when running Che in a Docker container:
-i, --image Launches Che within a Docker container using latest image
-i:tag, --image:tag Launches Che within a Docker container using specific image
-c:name, --container:name Sets the container name if -i provided; default=che
-t, --stop-container If stopping Che, will also stop Che container if Che ran with -i

Commands:
run (Default) Starts Che server with logging in current console
start Starts Che server in new console
stop Stops Che server

Docs: http://eclipse.org/che/getting-started.

If you are running Che as a server on a VM for multiple users to access, review the various networking
configuration items that control how clients, Che and workspaces initiate connections. See:
https://eclipse-che.readme.io/docs/networking.

[ghost]

Yes, docker ps failure message comes from the container. In fact, it is a startup script that runs this command and checks response code.

Che in Docker is still experimental. We have come to a conclusion that mounting /var/run/docker.sock is a way to avoid Docker in Docker since a server is launched n a container that then invokes creation of another container - this time a workspace container.

I suspect these are some sorts of permission issues for /var/run/docker.sock. It is also possible that different filesystems may have caused it as well.

There's another solution though. No unix socket mounting this time. You can run your local Docker daemon in a tcp mode and export DOCKER_HOST in the container, so that when Che server attempts to talk to a Docker daemon, it actually talks to it over tpc.

An easy way to check it is to restart Docker deamon in tcp mode and pass DOCKER_HOST env variable to a server container:

-e "DOCKER_HOST=tcp://yourIP:2375"

I'l add a short section in docs.

[ghost]

Here's what's worth trying - https://eclipse-che.readme.io/v4.0/docs/usage-docker#unix-socket-mounting-vs-exporting-docker_host

[ghost]

@JAZ-013 can't you run Che natively as well? I mean, just run che.sh run? No Docker involved.

[ghost]

@boban74 @JAZ-013 are you still having issues with running Che?

[boban74]

Hi eivantsov,

I still have the same issue ... tested it again on Ubuntu 16.04 with Eclipse Che 4.0.1

[JAZ-013]

Still got exact same error. Kubuntu 16.04 with Che 4.0.1

[ghost]

@boban74 @JAZ-013 Looks like Ubuntu 16 specific issue. Are we talking about running Che natively? Che is docker is still experimental.

[ghost]

Error writing 8192 bytes issue confirmed.

I have also been able to find out what causes the issue with Che in Docker. It's Docker version in Che container. I'll rebuild the image to make sure it uses 1.10.x vs 1.9.1 that it's using now. Thanks for sharing details that helped me figure it out.

[ghost]

@boban74 @JAZ-013 This is how you may want to try it in Docker right now:

docker run -ti --net=host -v /var/run/docker.sock:/var/run/docker.sock -v /home/user/che/lib:/home/user/che/lib-copy -v /home/user/che/workspaces:/home/user/che/workspaces -v /home/user/che/tomcat/temp/local-storage:/home/user/che/tomcat/temp/local-storage codenvy/che sh -c "sudo apt-get update && sudo apt-get install docker-engine -y && sudo chown -R user:user /home/user && rm -rf /home/user/che/lib-copy/* && mkdir -p /home/user/che/lib-copy/ && cp -rf /home/user/che/lib/* /home/user/che/lib-copy && /home/user/che/bin/che.sh run"

Bear in mind that you will need to keep permissions for var/run/docker.sock as read/write for others since GID for docker differ in Ubuntu 16 and Che container.

Finally, if you run Che in Docker in a VM, add -e "CHE_DOCKER_MACHINE_HOST=${VM-IP}" where ${VM-IP} is an actual IP address of your VM. Sure thing, 8080 and ephemeral port range have to be externally available.

[boban74]

Hi eivantsov,

yes, last test I've done was running Eclipse Che 4.0.1 on Ubuntu 16.04 natively ... and still got the error message running the workspace. The exception is the same already posted it on previous posts.

Thanks again,
Boban

[JAZ-013]

@eivantsov I've been trying to run it natively only. I don't know enough about docker to run che in docker I'm afraid. I think I tried it when Che wouldn't work for me initially, but I had a similar error.

[ghost]

I confirm both bugs now. Updating Docker version in Che base image isn't a big deal. Investigation on Ubuntu 16 failure might take some time.

[james10174]

@eivantsov Have you completed updating the docker version in Che base image? If so how do I download?

[ghost]

Will do early next week.

[ghost]

@james10174 codenvy/che:nightly has been updated

[james10174]

@eivantsov Hey thanks for getting that done. Your awesome ;) I will test it out soon. Right now I am actually creating cloud arm server with scaleway.com. Pretty fast just need to get che running on it. I will send you a link to the che server running on it when I am done. Not sure if anyones done something like this before. Just started using the service yesterday and so far it's been pretty nice but still really NOOB.

[JaegerP]

+1 on Arch Linux with amd64 Kernel v. 4.5.4, java 1.8.0u65 and docker 1.11.1.

2016-05-24 01:46:19,603[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 538] - Failed writing 8192 bytes
org.eclipse.che.api.machine.server.exception.MachineException: Failed writing 8192 bytes
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:405) ~[che-core-api-machine-4.2.0.jar:4.2.0]

See appended file for full stack trace.
stacktrace.txt
Just a guess, since ubuntu 16.04 also kernel 4.4.*: Could this problem be triggered to the changes in the linux container api made in 4.4.0?

[ghost]

@JaegerP thanks for reporting it. I'll escalate this issue.

[amiga23]

On a Raspberry Pi 2 with kernel 4.4.13-1-ARCH, on an Odroid XU4 with kernel 3.10.96-5-ARCH and on an AMD64 with kernel 4.6.2-1-ARCH I do also get the Error:
org.eclipse.che.api.machine.server.exception.MachineException: Failed writing 8192 bytes
Che version 4.2.0
docker version 1.11.2

[TylerJewell]

@amiga23 - Can you try it with the nightly build, please? 4.3.0 is in RC stage with 350 improvements.

[ghost]

@TylerJewell i do not think it will change the situation. This error has been reported by multiple users, including those on Ubuntu 16

[l0rd]

If the issue is related to different versions of the Docker client (running inside Che container) and Docker daemon (running on Docker host) a workaround is to add -v /usr/bin/docker:/usr/bin/docker to the docker run command.

[JaegerP]

@TylerJewell @l0rd tried with current nightly build (4.4.0), with and w/o
-v /usr/bin/docker:/usr/bin/docker:
Still
[ERROR] Failed writing 8192 bytes.
See che.log.txt

Full Command was

docker run 
    -ti --net=host --name che
    -v /var/run/docker.sock:/var/run/docker.sock
    -v /home/user/che/lib:/home/user/che/lib-copy 
    -v /home/user/che/workspaces:/home/user/che/workspaces 
    -v /home/user/che/tomcat/temp/local-storage:/home/user/che/tomcat/temp/local-storage 
    -v /usr/bin/docker:/usr/bin/docker 
    codenvy/che:nightly

[james10174]

@JaegerP Do you have swap memory? I have had problem with running out of memory on my beaglebone that only has 1gb like the raspberry pi 2.

[ghost]

I think it has smth to do with kernel version. Definitely needs a thorough investigation.

[JaegerP]

@james10174 I do not think so. I have 8GB RAM and 16GB swap, so that should be fine. Unfortunately, kernel v4.6.0 broke my installation completely. I am still investigating what is going wrong there.

[ghost]

I used to reliably reproduce this with Ubuntu 16. But now I cannot. Just started a clean Ubuntu 16 machine with Java and the latest Docker. The latest nightly build ran OK. Both natively and as a Docker container.

The kernel is 4.4.0-24-generic

[JAZ-013]

Due to @eivantsov's post, I decided to give it another crack. Not a fresh install, but Ubuntu 16 with 4.4.0-25-generic kernel and still no go for me. Docker is 1.10.3-0ubuntu6 if that matters.

[ghost]

Just tried to update Ubuntu 14 to Ubuntu 16. However, got the same kernel version. No issues. Now I do not have the right environment to reliably reproduce the issue.

[james10174]

I ran ran on ubuntu with no issues on scaleways.

root@scw-5b8d2c:~# uname -a
Linux scw-5b8d2c 4.5.2-docker-2 #1 SMP Fri Apr 29 08:57:24 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
root@scw-5b8d2c:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04 LTS
Release:        16.04
Codename:       xenial
docker-compose --version
docker-compose version 1.7.1, build 6c29830
docker --version
Docker version 1.11.1, build 5604cbe
docker info
Containers: 8
 Running: 4
 Paused: 0
 Stopped: 4
Images: 8
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 93
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: null host bridge
Kernel Version: 4.5.2-docker-2
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.857 GiB
Name: scw-5b8d2c
ID: GQB2:KOK6:KEFI:CZLX:D7N7:5YOI:WOZ4:ARFV:BJC6:5IJW:FSJ2:NREJ
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
Labels:
 provider=scaleway
/opt/jdk1.8.0_91/bin/java -version
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

Please letus know the output of the following
docker-compose --version
docker --version
docker info

[amiga23]

@TylerJewell I did also try with version assembly-main-4.4.0-RC1-20160614.152321-6.zip, does also not work. I guess it is because of the newer version of docker and you talk to it via the socket directly?!?

[james10174]

@amiga23 I am running docker 1.11.1 so I don't think it's the newer version of docker as long as you are using the nightly or zip file you are indicating.

[amiga23]

With a version directly from jenkins today "assembly-main-4.4.0-RC1-20160623.083628-29.tar.gz" it works fine now on AMD64 ArchLinux. I will test on Raspberry Pi 2 and Odroid XU4 later.

[amiga23]

Does also work on Raspberry Pi 2 ArchLinux. The above mentioned pull request fixed it.
I've created an PKGBUILD to install Che with makepkg on ArchLinux ARM:
https://github.com/amiga23/aur-eclipse-che-arm

[TylerJewell]

@amiga23 - really happy about this. Thanks for being persistent. We hope you enjoy the product.