Che Server not starting via docker machine

Description of problem: Running che.sh does not start the che server. Che version: 4.0.0-RC11 Che install directory: /Users/rrpolanco Docker version: Docker version 1.8.1 Java version: 1.8 Environment details (AWS, VirtualBox, physical, etc.): virtualbox How reproducible: I have the following docker-machine (via docker-machine ls):

NAME   ACTIVE   DRIVER       STATE     URL   SWARM
dev             virtualbox   Stopped

When I run che.sh, I get the following output:

Could not find an existing docker machine.
Creating docker machine named default... Please be patient, this takes a couple minutes the first time.
Successfully started docker machine named default...

The che script doesn’t seem to create a docker-machine named default nor does it run the server.

Am I missing something?

[TylerJewell]

Huh. Vbox has its quirks for sure. We are excited by the native docker for Mac coming soon. No more vbox setup required.

[TylerJewell]

@james10174 I am playing with the Docker for Windows Beta now. It’s gorgeous.

The improvements necessary to the che.sh script will not be that much. Essentially, if it’s installed, then we remove our dependency on Virtual Box or docker-machine, which ultimately guts about 33% of the script out. Essentially, we can treat all systems like Linux (remove all the OS checks, not have to do verifications on virtual box setup, etc.)

The new product requires hyperv under the covers though. And Hyperv is not universally provided on all Windows systems. It’s not on Windows Home, for example. So we may not be able to discontinue support for docker machine.