Docker machine driver for VMware Fusion and Workstation.
Home Page: https://www.vmware.com/products/personal-desktop-virtualization.html
License: Apache License 2.0
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
DHCP lease files are incorrect on Big Sur as networking now uses OS-provided facilities. One must use vmrun to get the correct guest IP.
See here for details: docker/machine#4846
Fixed by docker/machine#4847, which should apply here without much work.
Ironic that Fusion 12.1 now includes this at commit aaccce5 (which can't work), as listed in acknowledgements.pdf:
docker-machine-driver-vmware- aaccce554f6a23a80205520ade5b928d47ee9dec
I'm trying to use docker-machine (v0.16.1) with v0.1.0 of this driver on Windows 10 - 1903 with VMware Workstation 15 Pro.
Basic machine creation and usage works as expected BUT I would really, really like to use Bridged networking and not NAT.
If I manually change the configuration of a previously created machine to use bridged network then docker-machine never finds it's IP address.
DHCP is used on the bridged network and vmrun getGuestIPAddress returns the assigned address so why can't this driver pick it up?
We made a new driver, without the password:
It could be backported to docker-machine if needed.
It embeds the ssh keys on the disk image, instead.
Setup CI/CD pipeline to test master branch and pull requests.
Running #minikube start --driver vm
getting error
! 'vmware' driver reported an issue: exec: "docker-machine-driver-vmware": executable file not found in %PATH%
- Suggestion: Install docker-machine-driver-vmware
Installed from https://github.com/machine-drivers/docker-machine-driver-vmware/releases
Moved into %PATH%
Now getting error
Exiting due to DRV_UNSUPPORTED_OS: The driver 'vm' is not supported on windows/amd64
Is there any specific drivers for Intel Machines?
OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.17763 N/A Build 17763
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 142 Stepping 12 GenuineIntel ~1910 Mhz
I recently tried upgrading versions in my OS X development environment, and ran into issues starting a MySQL virtual machine due to issues accessing a hostPath persistent volume. The configuration I have works fine when using the vmwarefusion driver, but fails with the VMware driver.
minikube version: 1.0.1
kubernetes version: 1.14.1
vmware fusion version: 11.0.3 pro
The persistent volume is created with the following yams:
# Create local volumes for development MySQL instance
#
# Persistent Volume
apiVersion: v1
kind: PersistentVolume
metadata:
name: dev-db
labels:
type: local
spec:
accessModes:
- ReadWriteOnce
capacity:
storage: 5Gi
storageClassName: local-dev-db
hostPath:
path: /Users/eric/Development/wsv/localdev/dev-db-files
If I use the vmwarefusion driver with the configuration, mysql starts and runs fine. If I use the vmware driver, the mysql container errors during initialization with issues creating / accessing files in the data directory (which should be the persistent volume created above). Let me know what else is needed for debugging.
OS: Windows 10
Workstation: 15.1.0 build-13591040
Driver compiled from master branch with golang-1.10, minikube starts correctly and I can connect to it with a SSH client, but it would be nice if the created VMs would show up in the Workstation library.
Just a heads up that Go 1.17 (and the just-released 1.16 without first changing GO111MODULE) won't support builds that aren't in module-aware mode.
I'm not sure what the status of this project is (along with the other docker-machine-driver-* projects). Is there any plans to migrate to Go modules?
Hi @mikeroySoft, I commented this on my merged PR but creating this to increase visibility, would it be possible for you to do a release so I can get this change into kubernetes/minikube? A new release would resolve issues for our users, thanks!
Minishift is similar use case like minikube. It would be cool to those folks who are both minishift users and vmware fusion/workstation users. Similar to #1
Most Windows users don't have tar or gz installed. Windows supports zip natively. To enable Windows users to install this driver without installing additional archive management software, please publish future releases with zip files instead of/in addition to the tar.gz files.
docker-machine -D create --driver=vmware --vmware-cpu-count=2 --vmware-memory-size=4096 test
Machine test was created successfully but:
chmod: /mnt/hgfs/Users: Permission denied
fuse: mointpoint is not empty
fuse: if you are sure this is safe use the 'nonempty' mount option
fuse: mountpoint is not empty
fuse: if you are sure this is safe use the 'nonempty' mount option
So i cannot mount any directories in containers :(
There is no such problem with docker-machine-vmwareworkstation!
docker-machine-driver-vmware/pkg/drivers/vmware/driver.go
Lines 299 to 311 in abd4e62
These instructions needs the client tools to be available in the guest os, i was unable to install them after trying many times. How do i use a config drive (any pointer for this?) so that these instructions need not be run and a user does not have to install vmware-tools?
/cc @anfernee
Fusion has a newly designed REST API. It's a better model than current one which is heavily related to vmrun, in terms of
The only problem now is the REST API is only supported in Fusion. However, it's going to be supported in future version of workstation too, and it's fully compatible.
The windows integration test is missing.
minikube needs to register this driver to be able to use it. There is pending on a refactor in minikube so that it's easier to add drivers: kubernetes/minikube#2526
Hello, I'm the maintainer of https://github.com/pecigonzalo/docker-machine-vmwareworkstation, its really nice to see VMWare is now creating a driver that combines VMWare workstation and VMWare Fusion.
The mentioned repo is already added in the Docker docs as a driver, I believe it would be better to merge/support the work was already done there so we can combine the efforts instead of split this even further.
When trying to use this driver with boot2docker.iso it fails because the network hardware emulator doesn't appear to be supported.
When trying to use packer instead to create the vm for me, I discovered that it only works if I set:
"ethernet0.virtualDev": "e1000"
I'm guessing the drivers needed for vmware are not included in boot2docker, or are out-of-date for Workstation 15 so vmxnet3 doesn't work.
I'm using VMWare Workstation Pro 15, Windows, boot2docker 18.09 and docker-machine 0.14.0, build 89b8332
I tried to create a Docker Machine with the boot2docker 18.06.1 ISO with both the built-in vmwarefusion driver and this vmware driver plugin from this repo, but with both I see an error mounting the shared folder into the VM.
I'm using VMware Fusion Pro 11.0.1 on macOS 10.14 and docker-machine 0.15.0 from Docker for Mac 18.06.1-ce-mac73.
With the machine-drivers/docker-machine-driver-vmware driver (here is the gist of the debug output) a machine is created, but there is no shared folder
$ docker-machine -D create -d vmware --vmware-boot2docker-url=https://github.com/boot2docker/boot2docker/releases/download/v18.06.1-ce/boot2docker.iso vm18061
~/code/boot2docker on master*
$ ls
Dockerfile LICENSE README.md comment.md stack.yml
~/code/boot2docker on master*
$ docker run -v $(pwd):/code alpine ls -a /code
.
..
-> lines 358ff of the debug output during creation shows errors Error: There was an error mounting the Shared Folders file system inside the guest operating system
With the vmwarefusion driver (here is the gist of the debug output) the creation aborts with an error.
$ docker-machine -D create -d vmwarefusion --vmwarefusion-boot2docker-url=https://github.com/boot2docker/boot2docker/releases/download/v18.06.1-ce/boot2docker.iso vmw18061
...
Error creating machine: Error in driver during machine creation: exit status 255
notifying bugsnag: [Error creating machine: Error in driver during machine creation: exit status 255]
# try to enable shared folder manually again:
$ "/Applications/VMware Fusion.app/Contents/Public/vmrun" -gu docker -gp tcuser enableSharedFolders /Users/stefan/.docker/machine/machines/vmw18061/vmw18061.vmx
Error: There was an error mounting the Shared Folders file system inside the guest operating system
Does anybody else experience this problem with VMware Fusion 11?
I tried to create Docker Machine with VMWare Fusion 10.1.5 and docker-mache 0.16.1, but I see an error mounting the shared folders.
I have tried to create the Docker Machine by running the following command:
docker-machine -D create --driver vmwarefusion vm
Docker Machine Version: 0.16.1, build cce350d
Found binary path at /usr/local/bin/docker-machine
Launching plugin server for driver vmwarefusion
Plugin server listening at address 127.0.0.1:64127
() Calling .GetVersion
Using API Version 1
() Calling .SetConfigRaw
() Calling .GetMachineName
(flag-lookup) Calling .GetMachineName
(flag-lookup) Calling .DriverName
(flag-lookup) Calling .GetCreateFlags
Found binary path at /usr/local/bin/docker-machine
Launching plugin server for driver vmwarefusion
Plugin server listening at address 127.0.0.1:64135
() Calling .GetVersion
Using API Version 1
() Calling .SetConfigRaw
() Calling .GetMachineName
(vm) Calling .GetMachineName
(vm) Calling .DriverName
(vm) Calling .GetCreateFlags
(vm) Calling .SetConfigFromFlags
Reading certificate data from /Users/suin/.docker/machine/certs/ca.pem
Decoding PEM data...
Parsing certificate...
Reading certificate data from /Users/suin/.docker/machine/certs/cert.pem
Decoding PEM data...
Parsing certificate...
Running pre-create checks...
(vm) Calling .PreCreateCheck
(vm) DBG | local Boot2Docker ISO version: v18.09.5
(vm) Calling .GetConfigRaw
Creating machine...
(vm) Calling .Create
(vm) DBG | local Boot2Docker ISO version: v18.09.5
(vm) Copying /Users/suin/.docker/machine/cache/boot2docker.iso to /Users/suin/.docker/machine/machines/vm/boot2docker.iso...
(vm) Creating SSH key...
(vm) Creating VM...
(vm) Creating disk '/Users/suin/.docker/machine/machines/vm/vm.vmdk'
(vm) Virtual disk creation successful.
(vm) Starting vm...
(vm) DBG | executing: /usr/local/bin/vmrun start /Users/suin/.docker/machine/machines/vm/vm.vmx nogui
(vm) Waiting for VM to come online...
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | SSH Daemon not responding yet: dial tcp 192.168.113.129:22: i/o timeout
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | SSH Daemon not responding yet: dial tcp 192.168.113.129:22: i/o timeout
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | SSH Daemon not responding yet: dial tcp 192.168.113.129:22: i/o timeout
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | SSH Daemon not responding yet: dial tcp 192.168.113.129:22: connect: host is down
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | SSH Daemon not responding yet: dial tcp 192.168.113.129:22: connect: host is down
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | SSH Daemon not responding yet: dial tcp 192.168.113.129:22: connect: host is down
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | SSH Daemon not responding yet: dial tcp 192.168.113.129:22: connect: host is down
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | SSH Daemon not responding yet: dial tcp 192.168.113.129:22: connect: host is down
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | SSH Daemon not responding yet: dial tcp 192.168.113.129:22: connect: connection refused
(vm) DBG | executing: /usr/local/bin/vmrun list
(vm) DBG | MAC address in VMX: 00:0c:29:c9:dc:d6
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.59.1]
(vm) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vm) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.113.1]
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vm) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vm) DBG | IP found in DHCP lease table: 192.168.113.129
(vm) DBG | Got an ip: 192.168.113.129
(vm) DBG | Creating Tar key bundle...
(vm) DBG | executing: /usr/local/bin/vmrun -gu docker -gp tcuser directoryExistsInGuest /Users/suin/.docker/machine/machines/vm/vm.vmx /var/lib/boot2docker
(vm) DBG | executing: /usr/local/bin/vmrun -gu docker -gp tcuser CopyFileFromHostToGuest /Users/suin/.docker/machine/machines/vm/vm.vmx /Users/suin/.docker/machine/machines/vm/userdata.tar /home/docker/userdata.tar
(vm) DBG | executing: /usr/local/bin/vmrun -gu docker -gp tcuser runScriptInGuest /Users/suin/.docker/machine/machines/vm/vm.vmx /bin/sh sudo sh -c "tar xvf /home/docker/userdata.tar -C /home/docker > /var/log/userdata.log 2>&1 && chown -R docker:staff /home/docker"
(vm) DBG | executing: /usr/local/bin/vmrun -gu docker -gp tcuser runScriptInGuest /Users/suin/.docker/machine/machines/vm/vm.vmx /bin/sh sudo /bin/mv /home/docker/userdata.tar /var/lib/boot2docker/userdata.tar
(vm) DBG | executing: /usr/local/bin/vmrun -gu docker -gp tcuser enableSharedFolders /Users/suin/.docker/machine/machines/vm/vm.vmx
Error creating machine: Error in driver during machine creation: exit status 255
notifying bugsnag: [Error creating machine: Error in driver during machine creation: exit status 255]
Also, I tried to run vmrun manually and I got an error message like below:
/usr/local/bin/vmrun -gu docker -gp tcuser enableSharedFolders /Users/suin/.docker/machine/machines/vm/vm.vmx
Error: There was an error mounting the Shared Folders file system inside the guest operating system
Does anyone have an idea to solve this?
I tried to setup docker based on VMware Fusion for setup emulator inside container
According to instruction from readme file I:
Have an error:
Driver "vmware" not found. Do you have the plugin binary "docker-machine-driver-vmware" accessible in your PATH?
Also I tried with Go:
Please help with setup
Thanks,
Is this available on Homebrew?
Hello!
I recently found this plugin. So there are two docker-machine driver plugins for Windows VMware Workstation.
This one is great as it has Linux support which I'm looking for to have a Linux driver for WSL (but that' probably another issue/pull request).
A cool start would be a Chocolatey package so Windows users can easily install it.
As I've made the choco package for the other driver I adjusted the package code and it already works:
PS C:\> choco install -y vmwareworkstation docker docker-machine
PS C:\> choco install docker-machine-vmware -pre -source .
Chocolatey v0.10.11
Installing the following packages:
docker-machine-vmware
By installing you accept licenses for the packages.
docker-machine-vmware v0.1.0
docker-machine-vmware package files install completed. Performing other installation steps.
The package docker-machine-vmware wants to run 'chocolateyinstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[N]o/[P]rint): y
C:\ProgramData\chocolatey\lib\docker-machine-vmware\bin
Downloading docker-machine-vmware 64 bit
from 'https://github.com/machine-drivers/docker-machine-driver-vmware/releases/download/v0.1.0/docker-machine-driver-vmware_windows_amd64.exe'
Progress: 100% - Completed download of C:\ProgramData\chocolatey\lib\docker-machine-vmware\bin\docker-machine-driver-vmware.exe (6.87 MB).
Download of docker-machine-driver-vmware.exe (6.87 MB) completed.
Hashes match.
C:\ProgramData\chocolatey\lib\docker-machine-vmware\bin\docker-machine-driver-vmware.exe
ShimGen has successfully created a shim for docker-machine-driver-vmware.exe
The install of docker-machine-vmware was successful.
Software install location not explicitly set, could be in package or
default install location if installer.
Chocolatey installed 1/1 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Did you know the proceeds of Pro (and some proceeds from other
licensed editions) go into bettering the community infrastructure?
Your support ensures an active community, keeps Chocolatey tip top,
plus it nets you some awesome features!
https://chocolatey.org/compare
PS C:\vagrant\choco-docker-machine-vmware> docker-machine create -d vmware default
Creating CA: C:\Users\vagrant\.docker\machine\certs\ca.pem
Creating client certificate: C:\Users\vagrant\.docker\machine\certs\cert.pem
Running pre-create checks...
(default) Image cache directory does not exist, creating it at C:\Users\vagrant\.docker\machine\cache...
(default) No default Boot2Docker ISO found locally, downloading the latest release...
(default) Latest release for github.com/boot2docker/boot2docker is v18.06.0-ce
(default) Downloading C:\Users\vagrant\.docker\machine\cache\boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v18.06.0-ce/boot2docker.iso...
(default) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
Creating machine...
(default) Copying C:\Users\vagrant\.docker\machine\cache\boot2docker.iso to C:\Users\vagrant\.docker\machine\machines\default\boot2docker.iso...
(default) Creating SSH key...
(default) Creating VM...
(default) Starting default...
(default) Waiting for VM to come online...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: C:\ProgramData\chocolatey\lib\docker-machine\bin\docker-machine.exe env default
PS C:\> docker-machine env | iex
PS C:\> docker version
Client:
Version: 17.10.0-ce
API version: 1.33
Go version: go1.8.3
Git commit: f4ffd25
Built: Tue Oct 17 19:00:02 2017
OS/Arch: windows/amd64
Server:
Version: 18.06.0-ce
API version: 1.38 (minimum version 1.12)
Go version: go1.10.3
Git commit: 0ffa825
Built: Wed Jul 18 19:13:39 2018
OS/Arch: linux/amd64
Experimental: false
Do you want to take over the choco package sources into this repo so it can be added to a release step to build and push the choco package eg. from an AppVeyor CI build.
The choco package sources are at https://github.com/StefanScherer/choco-docker-machine-vmware and you can find a first successful build of the choco package and a small test if the driver works theoretically.
https://ci.appveyor.com/project/StefanScherer/choco-docker-machine-vmware/build/0.1.0.2
AppVeyor can't run VMware VM's, but the driver at least creates the machine folder.
So it's some kind of integration test.
https://github.com/AZ-X/docker-machine-driver-vmware
Thanks for attention unless nobody visits.
Im installed from here: https://community.chocolatey.org/packages/docker-machine-vmware#upgrade. But not lastest version (0.1.0). How to upgrade to new version?
Building deck for VMware SIG, @cantbewong to review and add to it.
From: kubernetes/minikube#2061
As stated in the minikube issue, I have this problem when using the vmware or the vmwarefusion drivers. When using the date command, the timezone is UTC but the time is my localtime.
This doesn't happen with the virtualbox driver.
I am trying to install minikube on an m1 mac and use the vmware driver option noted here: https://minikube.sigs.k8s.io/docs/drivers/vmware/
As noted in kubernetes/minikube#12858, the following issue comes up after following the minikube instructions:
minikube start --driver=vmware
😄 minikube v1.25.1 on Darwin 12.0.1 (arm64)
✨ Using the vmware driver based on user configuration
❌ Exiting due to DRV_UNSUPPORTED_OS: The driver 'vmware' is not supported on darwin/arm64
Per the minikube instructions, I installed the vmware driver via brew install docker-machine-driver-vmware.
I'm running OS X 10.13.6. After downloading updated driver according to README.md instructions I can't find the docker-machine-driver-vmware binary.
$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware Fusion.app/Contents/Public:/usr/local/MacGPG2/bin:/usr/local/go/bin
$ docker-machine-driver-vmware
-bash: docker-machine-driver-vmware: command not found
$ docker-machine create --driver=vmware vm1
Driver "vmware" not found. Do you have the plugin binary "docker-machine-driver-vmware" accessible in your PATH?
At the moment using Docker, Docker Machine with VMware on a Windows 10 machine in WSL looks like this:
The user has to think which part should be installed in WSL or directly in Windows.
With this driver I guess it should be easy to adjust the Linux part to recognize that it's running in WSL and searches for the vmrun.exe in the Windows file system. Then the installation looks like this:
WDYT?
On Ubuntu 18.04 on VMware WS, vmware driver doesn't work
$ sudo minikube start --vm-driver vmware
😄 minikube v0.34.1 on linux (amd64)
🔥 Creating vmware VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
💣 Unable to start VM: create: Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting
but kvm2 does work.
$ sudo minikube start --vm-driver kvm2
😄 minikube v0.34.1 on linux (amd64)
🔥 Creating kvm2 VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
📶 "minikube" IP address is 192.168.39.155
🐳 Configuring Docker as the container runtime ...
✨ Preparing Kubernetes environment ...
💾 Downloading kubeadm v1.13.3
💾 Downloading kubelet v1.13.3
🚜 Pulling images required by Kubernetes v1.13.3 ...
🚀 Launching Kubernetes v1.13.3 using kubeadm ...
🔑 Configuring cluster permissions ...
🤔 Verifying component health .....
💗 kubectl is now configured to use "minikube"
🏄 Done! Thank you for using minikube!
Should I use kvm2 instead?
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.