-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error starting workspace, WorkspaceManager error #745
Comments
i had a same problem in Windows. i suspected that, this could be because of port conflicts. I restated my PC. It resolved it. |
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, |
@boban74 can you provide the full stracktrace plase? As to running in Docker, make sure |
Hi eivantsov, here is the full stack trace running Eclipse Che and starting a workspace ...
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 |
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 |
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, |
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 This way you get a shell into the container, and run |
Hi Eugene, I've run the codenvy/che image with
and there I run docker ps and get the error message
running Thanks a lot, regards |
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 |
Hi Eugene, just tried it again ... the same error message already posted in previous comment ... this are my permissions ... Thanks again, |
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:
Maybe it is Ubuntu 16 specific issue. Can you run Do you have a chance to try the same on a different machine or VM? Also, |
Hi Eugene, id outputs ... Running The logs, after changing the log level to SEVERE, are full of ... 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 |
Can you attach the entire log file for me to take a look? |
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, |
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. |
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 I'm then able to run !!! Usage: Options when running Che natively: Options when running Che in a Docker container: Commands: 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 |
Yes, 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:
I'l add a short section in docs. |
Here's what's worth trying - https://eclipse-che.readme.io/v4.0/docs/usage-docker#unix-socket-mounting-vs-exporting-docker_host |
@JAZ-013 can't you run Che natively as well? I mean, just run che.sh run? No Docker involved. |
Hi eivantsov, I still have the same issue ... tested it again on Ubuntu 16.04 with Eclipse Che 4.0.1 |
Still got exact same error. Kubuntu 16.04 with Che 4.0.1 |
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. |
@boban74 @JAZ-013 This is how you may want to try it in Docker right now:
Bear in mind that you will need to keep permissions for Finally, if you run Che in Docker in a VM, add |
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, |
@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. |
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. |
@eivantsov Have you completed updating the docker version in Che base image? If so how do I download? |
Will do early next week. |
@james10174 codenvy/che:nightly has been updated |
@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. |
+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 See appended file for full stack trace. |
@JaegerP thanks for reporting it. I'll escalate this issue. |
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: |
@amiga23 - Can you try it with the nightly build, please? 4.3.0 is in RC stage with 350 improvements. |
@TylerJewell i do not think it will change the situation. This error has been reported by multiple users, including those on Ubuntu 16 |
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 |
@TylerJewell @l0rd tried with current nightly build (4.4.0), with and w/o 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 |
@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. |
I think it has smth to do with kernel version. Definitely needs a thorough investigation. |
@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. |
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 |
Due to @eivantsov's post, I decided to give it another crack. Not a fresh install, but Ubuntu 16 with |
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. |
I ran ran on ubuntu with no issues on scaleways.
Please letus know the output of the following |
@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?!? |
@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. |
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. |
Does also work on Raspberry Pi 2 ArchLinux. The above mentioned pull request fixed it. |
@amiga23 - really happy about this. Thanks for being persistent. We hope you enjoy the product. |
_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
The text was updated successfully, but these errors were encountered: