-
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
Run on docker for windows #1695
Comments
@mariotoffia - when you are on Docker for Windows, there is some additional configuration required. We have an explanation of what is needed on this page dedicated to Docker for Windows: |
Hi and thanks for prompt answer! Yes - me bad - just read the server topic and thought that docker for windows was just about running che in a docker container Cheers, |
@TylerJewell Seems like it still needs the export DOCKER_TOOLBOX_INSTALL_PATH=${PROGRAMFILES}\Docker\Docker\resources\bin in order to work - but then it does (maybe update docs? :) Cheers, |
It shouldn't, by nature. But your path does need the docker client included which should happen when docker for Windows is installed. |
@TylerJewell Sorry for bothering you again, but I come to that it will pull the "codenvy/ubuntu_jdk8" image (and ubuntu) it labels the image when im trying to access the project "eclipse-che/workspaceor3rbog4y65fnop0_machine58ct8xu7hmwyr25e_che_default" but it throws exception and cannot start the image (seems like it uses docker machine? - that can't be correct or?). Cheers, This is my exception: |
Can you paste the full syntax of your run command and then the url you used to access the system? |
@TylerJewell Absolutely. Added two lines of export for DOCKER_HOST / TOOLBOX after 'trap exit SIGHUP SIGINT SIGTERM' line in che.sh: Run: ./che.sh run ..and the socket reset error occurs. Shall I increase logging verbosity? Cheers, |
Please, do not modify the che.sh script. You are causing unintended consequences. Make sure you do everything outside of the script and follow the sequence on the docs very carefully. Do you get the same issue when you create a new workspace, or just when you choose a recent workspace? |
Yes, I get the same - It seems to work one of 10-20 or so. I have set of steps where I mostly fails but sometimes it succeeds.
Output:
Output:
Output:
Ha've no specific pattern that I've spotted - It seems to do the docker build (tagging the image) and then fail but two of around 15 - 20 times did work. Cheers, |
@mariotoffia - what happens if you just run the follwoing. Note the two places where you should choose a local directory and replace our stuff:
|
Hi, I've modified che.sh so it do not use docker-machine on windows. I'm using docker for windows and thus only "pure" client docker access is needed.
When I create a workspace and hit start: It will throw an exception since it cannot find the certificates (see stack trace).
Is it possible to get it to run under docker for windows?
Cheers,
Mario
Reproduction Steps:
Expected behavior:
Create a new instance of a docker container containing the project (in my case plain Java project).
Observed behavior:
Complaints about missing certificate for docker https daemon communication ("Certificates are required for https connection.") and throws a stack trace in catalina.out.
Che version: 4.4.0
OS and version: Windows 10
Docker version: Docker for windows RC3 (1.12.0-rc3-beta18) - API Version 1.24
Che install: server (zip)
Additional information:
Stacktrace:
2016-07-08 19:37:17,722[kspaceManager-0] [ERROR] [o.e.c.a.w.s.WorkspaceManager 567] - Certificates are required for https connection.
java.lang.IllegalArgumentException: Certificates are required for https connection.
at org.eclipse.che.plugin.docker.client.connection.TcpConnection.(TcpConnection.java:41) ~[che-plugin-docker-client-4.4.0.jar:4.4.0]
at org.eclipse.che.plugin.docker.client.connection.DockerConnectionFactory.openConnection(DockerConnectionFactory.java:52) ~[che-plugin-docker-client-4.4.0.jar:4.4.0]
at org.eclipse.che.plugin.docker.client.DockerConnector.pull(DockerConnector.java:1504) ~[che-plugin-docker-client-4.4.0.jar:4.4.0]
at org.eclipse.che.plugin.docker.client.DockerConnector.pull(DockerConnector.java:1484) ~[che-plugin-docker-client-4.4.0.jar:4.4.0]
at org.eclipse.che.plugin.docker.machine.local.interceptor.EnableOfflineDockerMachineBuildInterceptor.pullImage(EnableOfflineDockerMachineBuildInterceptor.java:73) ~[che-plugin-docker-machine-4.4.0.jar:4.4.0]
at org.eclipse.che.plugin.docker.machine.local.interceptor.EnableOfflineDockerMachineBuildInterceptor.invoke(EnableOfflineDockerMachineBuildInterceptor.java:58) ~[che-plugin-docker-machine-4.4.0.jar:4.4.0]
at org.eclipse.che.plugin.docker.machine.DockerInstanceProvider.createInstance(DockerInstanceProvider.java:315) ~[che-plugin-docker-machine-4.4.0.jar:4.4.0]
at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:376) ~[che-core-api-machine-4.4.0.jar:4.4.0]
at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:337) ~[che-core-api-machine-4.4.0.jar:4.4.0]
at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:165) ~[che-core-api-machine-4.4.0.jar:4.4.0]
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582) ~[che-core-api-workspace-4.4.0.jar:4.4.0]
The text was updated successfully, but these errors were encountered: