Codenvy in Docker: Fail to start a workspace on Windows

[ghost]

Running a workspace results in the following error:

Win 10

[riuvshin]

It seems I've reproduced same issue on mac. In my cause I've tried to configure and use codenvy with real dns.

after revert back to ip it works again.

2016-11-08 21:49:28,052[kspaceManager-1]  [ERROR] [o.e.c.a.w.s.WorkspaceManager 664]    - Start of environment default failed. Error: Restoring of workspace workspacebl5clemwbogkujmg filesystem terminated on aio.codenvy-dev.com node. Process failed. Exit code 255
org.eclipse.che.api.core.ServerException: Start of environment default failed. Error: Restoring of workspace workspacebl5clemwbogkujmg filesystem terminated on aio.codenvy-dev.com node. Process failed. Exit code 255
    at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:279) ~[che-core-api-workspace-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$1(WorkspaceManager.java:648) ~[che-core-api-workspace-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) ~[che-core-commons-lang-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_102]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_102]
    at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_102]
Caused by: org.eclipse.che.api.machine.server.exception.MachineException: Restoring of workspace workspacebl5clemwbogkujmg filesystem terminated on aio.codenvy-dev.com node. Process failed. Exit code 255
    at com.codenvy.machine.RemoteDockerNode.bindWorkspace(RemoteDockerNode.java:132) ~[codenvy-machine-hosted-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    at com.codenvy.machine.launcher.RsyncAgentLauncherImpl.launch(RsyncAgentLauncherImpl.java:58) ~[codenvy-machine-hosted-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.launchAgents(WorkspaceRuntimes.java:656) ~[che-core-api-workspace-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.launchAgents(WorkspaceRuntimes.java:297) ~[che-core-api-workspace-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:253) ~[che-core-api-workspace-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    ... 5 common frames omitted
Caused by: org.eclipse.che.api.core.ServerException: Restoring of workspace workspacebl5clemwbogkujmg filesystem terminated on aio.codenvy-dev.com node. Process failed. Exit code 255
    at com.codenvy.machine.backup.MachineBackupManager.restoreWorkspaceBackup(MachineBackupManager.java:220) ~[codenvy-machine-hosted-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    at com.codenvy.machine.RemoteDockerNode.bindWorkspace(RemoteDockerNode.java:123) ~[codenvy-machine-hosted-5.0.0-hackathon-SNAPSHOT.jar:5.0.0-hackathon-SNAPSHOT]
    ... 9 common frames omitted

[TylerJewell]

Interesting. My windows configuration is - by default - IP only. Isn't that the default for all systems?

[riuvshin]

I can't reproduce this on mac or linux with IP. I wanted to test http \ https switch to provide proper docs but with configured DNS I can't start WS with exactly same error.
(btw this is real dns I;ve asked ADM team register real dns on godaddy for my IP to avoid pain with hosts)

[mkuznyetsov]

On Windows, there were problems with ssh key, that is used for rsync. (it's permissions are "too open", and cannot be changed on that exact file in container) which result in workspace startup failure.
It is solved by updating rsyncrestore.sh and rsyncbackup.sh scripts to use a copy of that key with correct permissions

[TylerJewell]

Worked perfectly on windows. +1 to merge and close.

BTW - the new checks for docker host mounts also worked! I had reset my docker for windows VM and it unsets the C drive. And the CLI discovered that and told me what to do.

[riuvshin]

cool!