Isn't the MobyLinuxVM the default docker-machine?

Docker Desktop for Windows
1

Expected behavior

After installing Docker for Windows, the default docker machine should be created, started and be available for use on docker-compose.

Actual behavior

Docker for Windows creates a VM called MobyLinuxVM consuming 2GB of RAM and when I run docker-machine ps is doesn’t show any docker machine. If I run docker-machine create -d “hyperv” default it creates a new VM cosuming 1GB of RAM.

Information

Diagnostic: BD1854A3-041C-4C22-9FE5-1E5045910B45/2016-06-29_21-55-53

Windows 10 x64

docker-compose.yml
version: ‘2’

services:
  wordpress:
    image: wordpress
    volumes: 
      - .:/var/www/html
    ports: 
      - "8080:8080"
    depends_on:
      - 'db'
    networks:
      - conadeps-network
    environment: 
      WORDPRESS_DB_PASSWORD: 'P@ssw0rd'
      

  db:
    image: mariadb
    environment: 
      MYSQL_ROOT_PASSWORD: 'P@ssw0rd'
    networks:
      - conadeps-network


networks:
  conadeps-network:
    driver: bridge

Steps to reproduce the behavior

  1. … Install Docker for Windows beta
  2. … Run it as administrator
  3. … Run docker-machine ps to list machines
1 Like
2

This is by design - Docker for Windows works differently than docker-machine. With Docker for Windows installed, we recommend using docker-machine only for remote machine creation

Basically, docker-machine expects the machine to be available through ssh which is not the case with the VM within docker for windows.

See Should MobyLinux appear in the results from "docker-machine ls" and "docker-machine ls" doesn't show MobyLinuxVM...is this correct?

1 Like
3

Thanks jeanlaurent, I assumed that it was probably a feature rather than a problem, since Windows is different from Linux. I just needed confirmation.

Cheers

JAV