I began uplifting some of my content today which included upgrading to the newest docker (v1.5) and docker-machine (v0.1), and came across a number of changes.
- The command is now officially “docker-machine” instead of just “machine” which is what it was when I first played with it.
- All the VMware driver commands are now prefixed with “vmware” so instead of “–vsphere-vcenter” it is now “–vmwarevsphere-vcenter” a full example is: 12345678docker-machine create -d vmwarevsphere--vmwarevsphere-vcenter="vcenter.corp.local" \--vmwarevsphere-username="firstname.lastname@example.org" \--vmwarevsphere-password="password" \--vmwarevsphere-datacenter="Datacenter" \--vmwarevsphere-compute-ip="192.168.110.xxx" \--vmwarevsphere-datastore="datastore" \--vmwarevsphere-network="VM Network" dockervm0
And they have an easier way to set the environment variables now:
1$(docker-machine env dockervm0)
- I couldn’t get “–vmwarevsphere-boot2docker-url” to work with a custom URL which is probably a bug. If you leave it out entirely it will use a default location.
- ..Which is a good thing because boot2docker now includes VMware tools, which negates the need for a custom .ISO
- The only other change I need to make to the boot2docker image is the use of a insecure registry, so I just include in my syntax the running of a shell script which runs: docker-machine ssh $1 “sudo sed -i -e ‘s/–tlsverify/–tlsverify –insecure-registry docker-hub:5000/g’ /var/lib/boot2docker/profile“ You can find this full shell script on github here. “docker-hub” is my registry hostname on port 5000
- I noticed the name of the VM now matches what docker-machine calls it instead of a random string.
That’s about it so far. I have not used it too extensively yet but so far so good. I did not see a single hang of the docker commands like I saw previously with the older versions. Thumbs up so far.