docker-machine create | Drivers

• ISSUE @ docker-machine @ Cloud (AWS) Machine(s)

  • Not communicating properly; can ssh, can init/join swarm, but fails to properly connect and report engine version etc; vpc and/or security group issue?

    docker-machine ls 
    #... does not report engine version etc.; "unable to connect".
    

• ISSUE @ v18.09.0 of boot2docker.iso. It breaks Swarm Ingress, so no internet connectivity; can ping but not browse (or curl, wget, …) to any exposed port(s) of any service.

  • Workaround by selecting another version, per "--hyperv-boot2docker-url" option …

    docker-machine create -d hyperv --hyperv-virtual-switch "External Switch" --hyperv-boot2docker-url \
        "https://github.com/boot2docker/boot2docker/releases/download/v18.06.1-ce/boot2docker.iso" \
        $_VM
    

  • FIXED? (Mar 3, 2019) @ v18.09.2 Yes, this is fixed.

    PS> docker-machine ssh h1                                                                              ( '>')
      /) TC (\   Core is distributed with ABSOLUTELY NO WARRANTY.
     (/-_--_-\)           www.tinycorelinux.net
    
    docker@h1:~$ uname -a
    Linux h1 4.19.130-boot2docker #1 SMP Mon Jun 29 23:52:55 UTC 2020 x86_64 GNU/Linux
    

    • Use Git for Windows (MINGW64) or PowerShell for all docker-machine commands.
      • WSL FAILs @ docker swarm join ...; only leader "joins", but not even it is "active" @ "docker-machine active" or docker-machine ls.
      • WSL 2 FAILs @ all things Docker.

docker-machine create--driver hyperv

• Must use Git for Windows (MINGW64) or PowerShell for all docker-machine tool commands
  • WSL cannot create its storage:
    • @ /c/HOME/.docker/machine/machines/vm2/fixed.vhd
  • WSL-created nodes fail @ ... swarm join ...
  • WSL 2 FAILs @ all things Docker.
• OS (boot2docker) Automatically installed, unlike other drivers, e.g., AWS.
  • Use default (latest); earlier-version issue (broke swarm) is resolved.