docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7643 from shin-/machine_update 

Update docs with latest version of docker-machine
This commit is contained in:
Maria Bermudez 2018-11-08 17:11:12 -08:00 committed by GitHub
parent 3afd6dd652 4a3bc78f09
commit 3669c4a264
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 157 additions and 118 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_config.yml
View File

@ -24,7 +24,7 @@ docker_ce_stable_version: "18.09"
docker_ce_edge_version: "18.09"
docker_ee_version: "2.1"
compose_version: "1.23.1"
machine_version: "0.14.0"
machine_version: "0.16.0"
distribution_version: "2.6"
dtr_version: "2.6"
ucp_version: "3.1"

113
machine/drivers/aws.md
View File

@ -46,73 +46,75 @@ You can use environment variables:
- `--amazonec2-ami`: The AMI ID of the instance to use.
- `--amazonec2-block-duration-minutes`: AWS spot instance duration in minutes (60, 120, 180, 240, 300, or 360).
- `--amazonec2-device-name`: The root device name of the instance.
- `--amazonec2-endpoint`: Optional endpoint URL (hostname only or fully qualified URI)
- `--amazonec2-endpoint`: Optional endpoint URL (hostname only or a fully qualified URI).
- `--amazonec2-iam-instance-profile`: The AWS IAM role name to be used as the instance profile.
- `--amazonec2-insecure-transport`: Disable SSL when sending requests
- `--amazonec2-insecure-transport`: Disable SSL when sending requests.
- `--amazonec2-instance-type`: The instance type to run.
- `--amazonec2-keypair-name`: AWS keypair to use; requires --amazonec2-ssh-keypath
- `--amazonec2-keypair-name`: AWS keypair to use; requires `--amazonec2-ssh-keypath`.
- `--amazonec2-monitoring`: Enable CloudWatch Monitoring.
- `--amazonec2-open-port`: Make the specified port number accessible from the Internet.
- `--amazonec2-private-address-only`: Use the private IP address only.
- `--amazonec2-region`: The region to use when launching the instance.
- `--amazonec2-request-spot-instance`: Use spot instances.
- `--amazonec2-retries`: Set retry count for recoverable failures (use -1 to disable)
- `--amazonec2-retries`: Set retry count for recoverable failures (use `-1` to disable).
- `--amazonec2-root-size`: The root disk size of the instance (in GB).
- `--amazonec2-secret-key`: Your secret access key for the Amazon Web Services API.
- `--amazonec2-security-group`: AWS VPC security group name.
- `--amazonec2-security-group-readonly`: Skip adding default rules to security groups.
- `--amazonec2-session-token`: Your session token for the Amazon Web Services API.
- `--amazonec2-spot-price`: Spot instance bid price (in dollars). Require the `--amazonec2-request-spot-instance` flag.
- `--amazonec2-ssh-keypath`: Path to Private Key file to use for instance. Matching public key with .pub extension should exist
- `--amazonec2-ssh-user`: The SSH Login username, which must match the default SSH user set in the ami used.
- `--amazonec2-spot-price`: Spot instance bid price in dollars. Requires the `--amazonec2-request-spot-instance` flag.
- `--amazonec2-ssh-keypath`: Path to private key file to use for instance. Requires a matching public key with `.pub` extension to exist.
- `--amazonec2-ssh-user`: The SSH login username, which must match the default SSH user set in the AMI being used.
- `--amazonec2-subnet-id`: AWS VPC subnet ID.
- `--amazonec2-tags`: AWS extra tag key-value pairs. Comma-separated. For example, `key1,value1,key2,value2`.
- `--amazonec2-use-ebs-optimized-instance`: Create an EBS Optimized Instance, instance type must support it.
- `--amazonec2-tags`: A comma-separated list of AWS extra tag key-value pairs. For example, `key1,value1,key2,value2`.
- `--amazonec2-use-ebs-optimized-instance`: Create an EBS Optimized Instance. Instance type must support it.
- `--amazonec2-use-private-address`: Use the private IP address for docker-machine, but still create a public IP address.
- `--amazonec2-userdata`: Path to file with cloud-init user data.
- `--amazonec2-volume-type`: The Amazon EBS volume type to be attached to the instance.
- `--amazonec2-vpc-id`: Your VPC ID to launch the instance in.
- `--amazonec2-zone`: The AWS zone to launch the instance in (one of a,b,c,d,e).
- `--amazonec2-zone`: The AWS zone to launch the instance in (one of a,b,c,d, and e).
#### Environment variables and default values:
| CLI option | Environment variable | Default |
|:-----------------------------------------|:-------------------------|:-----------------|
| `--amazonec2-access-key` | `AWS_ACCESS_KEY_ID` | - |
| `--amazonec2-ami` | `AWS_AMI` | `ami-c60b90d1` |
| `--amazonec2-block-duration-minutes` | - | - |
| `--amazonec2-device-name` | `AWS_DEVICE_NAME` | `/dev/sda1` |
| `--amazonec2-endpoint` | `AWS_ENDPOINT` | - |
| `--amazonec2-iam-instance-profile` | `AWS_INSTANCE_PROFILE` | - |
| `--amazonec2-insecure-transport` | `AWS_INSECURE_TRANSPORT` | - |
| `--amazonec2-instance-type` | `AWS_INSTANCE_TYPE` | `t2.micro` |
| `--amazonec2-keypair-name` | `AWS_KEYPAIR_NAME` | - |
| `--amazonec2-monitoring` | - | `false` |
| `--amazonec2-open-port` | - | - |
| `--amazonec2-private-address-only` | - | `false` |
| `--amazonec2-region` | `AWS_DEFAULT_REGION` | `us-east-1` |
| `--amazonec2-request-spot-instance` | - | `false` |
| `--amazonec2-retries` | - | `5` |
| `--amazonec2-root-size` | `AWS_ROOT_SIZE` | `16` |
| `--amazonec2-secret-key` | `AWS_SECRET_ACCESS_KEY` | - |
| `--amazonec2-security-group` | `AWS_SECURITY_GROUP` | `docker-machine` |
| `--amazonec2-session-token` | `AWS_SESSION_TOKEN` | - |
| `--amazonec2-spot-price` | - | `0.50` |
| `--amazonec2-ssh-keypath` | `AWS_SSH_KEYPATH` | - |
| `--amazonec2-ssh-user` | `AWS_SSH_USER` | `ubuntu` |
| `--amazonec2-subnet-id` | `AWS_SUBNET_ID` | - |
| `--amazonec2-tags` | `AWS_TAGS` | - |
| `--amazonec2-use-ebs-optimized-instance` | - | `false` |
| `--amazonec2-use-private-address` | - | `false` |
| `--amazonec2-userdata` | `AWS_USERDATA` | - |
| `--amazonec2-volume-type` | `AWS_VOLUME_TYPE` | `gp2` |
| `--amazonec2-vpc-id` | `AWS_VPC_ID` | - |
| `--amazonec2-zone` | `AWS_ZONE` | `a` |
| CLI option | Environment variable | Default |
|:-----------------------------------------|:------------------------------|:-----------------|
| `--amazonec2-access-key` | `AWS_ACCESS_KEY_ID` | - |
| `--amazonec2-ami` | `AWS_AMI` | `ami-c60b90d1` |
| `--amazonec2-block-duration-minutes` | - | - |
| `--amazonec2-device-name` | `AWS_DEVICE_NAME` | `/dev/sda1` |
| `--amazonec2-endpoint` | `AWS_ENDPOINT` | - |
| `--amazonec2-iam-instance-profile` | `AWS_INSTANCE_PROFILE` | - |
| `--amazonec2-insecure-transport` | `AWS_INSECURE_TRANSPORT` | - |
| `--amazonec2-instance-type` | `AWS_INSTANCE_TYPE` | `t2.micro` |
| `--amazonec2-keypair-name` | `AWS_KEYPAIR_NAME` | - |
| `--amazonec2-monitoring` | - | `false` |
| `--amazonec2-open-port` | - | - |
| `--amazonec2-private-address-only` | - | `false` |
| `--amazonec2-region` | `AWS_DEFAULT_REGION` | `us-east-1` |
| `--amazonec2-request-spot-instance` | - | `false` |
| `--amazonec2-retries` | - | `5` |
| `--amazonec2-root-size` | `AWS_ROOT_SIZE` | `16` |
| `--amazonec2-secret-key` | `AWS_SECRET_ACCESS_KEY` | - |
| `--amazonec2-security-group` | `AWS_SECURITY_GROUP` | `docker-machine` |
| `--amazonec2-security-group-readonly` | `AWS_SECURITY_GROUP_READONLY` | `false` |
| `--amazonec2-session-token` | `AWS_SESSION_TOKEN` | - |
| `--amazonec2-spot-price` | - | `0.50` |
| `--amazonec2-ssh-keypath` | `AWS_SSH_KEYPATH` | - |
| `--amazonec2-ssh-user` | `AWS_SSH_USER` | `ubuntu` |
| `--amazonec2-subnet-id` | `AWS_SUBNET_ID` | - |
| `--amazonec2-tags` | `AWS_TAGS` | - |
| `--amazonec2-use-ebs-optimized-instance` | - | `false` |
| `--amazonec2-use-private-address` | - | `false` |
| `--amazonec2-userdata` | `AWS_USERDATA` | - |
| `--amazonec2-volume-type` | `AWS_VOLUME_TYPE` | `gp2` |
| `--amazonec2-vpc-id` | `AWS_VPC_ID` | - |
| `--amazonec2-zone` | `AWS_ZONE` | `a` |
## Default AMIs
By default, the Amazon EC2 driver uses a daily image of Ubuntu 16.04 LTS.
By default, the Amazon EC2 driver uses a daily image of `Ubuntu 16.04 LTS`.
| Region | AMI ID |
| -------------- | ------------ |
@ -142,35 +144,32 @@ A security group is created and associated to the host. This security group has
- docker (2376/tcp)
- swarm (3376/tcp), only if the node is a swarm master
If you specify a security group yourself using the `--amazonec2-security-group` flag, the above ports are checked and opened and the security group modified.
If you want more ports to be opened, like application specific ports, use the AWS console and modify the configuration manually.
If you specify a security group yourself using the `--amazonec2-security-group` flag, the above ports are checked and opened and the security group is modified.
If you want more ports to be opened such as application-specific ports, use the AWS console and modify the configuration manually.
## VPC ID
We determine your default VPC ID at the start of a command.
In some cases, either because your account does not have a default vpc, or you don't want to use the default one, you can specify a vpc with the `--amazonec2-vpc-id` flag.
Your default VPC ID is determined at the start of a command. In some cases, either because your account does not have a default VPC, or you do not want to use the default one, you can specify a VPC with the `--amazonec2-vpc-id` flag.
To find the VPC ID:
### To find the VPC ID:
1. Login to the AWS console
1. Login to the AWS console.
2. Go to **Services -> VPC -> Your VPCs**.
3. Locate the VPC ID you want from the _VPC_ column.
4. Go to **Services -> VPC -> Subnets**. Examine the _Availability Zone_ column to verify that zone `a` exists and matches your VPC ID.
3. Locate the VPC ID you want from the *_VPC_* column.
4. Go to **Services -> VPC -> Subnets**. Examine the _Availability Zone_ column to verify that zone `a` exists and matches your VPC ID. For example, `us-east1-a` is in the `a` availability zone. If the `a` zone is not present, you can create a new subnet in that zone or specify a different zone when you create the machine.
For example, `us-east1-a` is in the `a` availability zone. If the `a` zone is not present, you can create a new subnet in that zone or specify a different zone when you create the machine.
To create a machine with a non-default VPC-ID:
### To create a machine with a non-default VPC-ID:
$ docker-machine create --driver amazonec2 --amazonec2-access-key AKI******* --amazonec2-secret-key 8T93C********* --amazonec2-vpc-id vpc-****** aws02
This example assumes the VPC ID was found in the `a` availability zone. Use the`--amazonec2-zone` flag to specify a zone other than the `a` zone. For example, `--amazonec2-zone c` signifies `us-east1-c`.
## VPC Connectivity
Machine uses SSH to complete the set up of instances in EC2 and requires the ability to access the instance directly.
Docker Machine uses SSH to complete the set up of instances in EC2 and requires the ability to access the instance directly.
If you use the flag `--amazonec2-private-address-only`, ensure that you can access the new instance from within the internal network of the VPC, such as a corporate VPN to the VPC, a VPN instance inside the VPC, or using `docker-machine` from an instance within your VPC.
Configuration of VPCs is beyond the scope of this guide, however the first step in troubleshooting is ensuring if you are using private subnets that you follow the design guidance in the [AWS VPC User Guide](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario2.html) and have some form of NAT available so that the set up process can access the internet to complete set up.
Configuration of VPCs is beyond the scope of this guide. However, the first step in troubleshooting is making sure that you are using private subnets that follow the design guidance in the [AWS VPC User Guide](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario2.html) and have some form of NAT available so that the setup process can access the internet to complete the setup.
## Custom AMI and SSH username
@ -178,4 +177,4 @@ The default SSH username for the default AMIs is `ubuntu`.
You need to change the SSH username only if the custom AMI you use has a different SSH username.
You can change the SSH username with the `--amazonec2-ssh-user` according to the AMI you selected with the `--amazonec2-ami`.
You can change the SSH username with the `--amazonec2-ssh-user` according to the AMI you selected with the `--amazonec2-ami` option.

63
machine/drivers/hyper-v.md
View File

@ -9,8 +9,8 @@ Creates a Boot2Docker virtual machine locally on your Windows machine
using Hyper-V.
Hyper-V must be enabled on your desktop system. Docker for Windows automatically
enables it upon install. See this article on the Microsoft developer network for
[instructions on how to manually enable
enables it upon install. See this article on the Microsoft developer network for instructions on
[how to manually enable
Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install).
> **Notes**:
@ -18,12 +18,12 @@ Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick
> * You must use an Administrator level account to create and manage Hyper-V machines.
>
>* You need an existing virtual switch to use the
> driver. Hyper-V can share an external network interface (aka
> bridging), see [this blog](http://blogs.technet.com/b/canitpro/archive/2014/03/11/step-by-step-enabling-hyper-v-for-use-on-windows-8-1.aspx).
> driver. Hyper-V can share an external network interface (also known as
> bridging). See [this blog](http://blogs.technet.com/b/canitpro/archive/2014/03/11/step-by-step-enabling-hyper-v-for-use-on-windows-8-1.aspx) to learn more.
> If you would like to use NAT, create an internal network, and use
> [Internet Connection Sharing](http://www.packet6.com/allowing-windows-8-1-hyper-v-vm-to-work-with-wifi/).
>
> * This reference page includes an [example](hyper-v.md#example) that shows how to use an elevated (Administrator-level) PowerShell and how to create and use an external network switch.
> * This reference page includes an [example](hyper-v.md#example) showing you how to use an elevated (Administrator-level) PowerShell and create and use an external network switch.
## Usage
@ -38,38 +38,40 @@ Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick
- `--hyperv-cpu-count`: Number of CPUs for the host.
- `--hyperv-static-macaddress`: Hyper-V network adapter's static MAC address.
- `--hyperv-vlan-id`: Hyper-V network adapter's VLAN ID if any.
- `--hyperv-disable-dynamic-memory`: Disable dynamic memory management.
## Environment variables and default values
| CLI option | Environment variable | Default |
| ---------------------------- | -------------------------- | ------------------------ |
| `--hyperv-boot2docker-url` | `HYPERV_BOOT2DOCKER_URL` | _Latest boot2docker url_ |
| `--hyperv-cpu-count` | `HYPERV_CPU_COUNT` | `1` |
| `--hyperv-disk-size` | `HYPERV_DISK_SIZE` | `20000` |
| `--hyperv-memory` | `HYPERV_MEMORY` | `1024` |
| `--hyperv-static-macaddress` | `HYPERV_STATIC_MACADDRESS` | _undefined_ |
| `--hyperv-virtual-switch` | `HYPERV_VIRTUAL_SWITCH` | _first found_ |
| `--hyperv-vlan-id` | `HYPERV_VLAN_ID` | _undefined_ |
| CLI option | Environment variable | Default |
| --------------------------------- | ------------------------------- | ------------------------ |
| `--hyperv-boot2docker-url` | `HYPERV_BOOT2DOCKER_URL` | _Latest boot2docker url_ |
| `--hyperv-cpu-count` | `HYPERV_CPU_COUNT` | `1` |
| `--hyperv-disk-size` | `HYPERV_DISK_SIZE` | `20000` |
| `--hyperv-memory` | `HYPERV_MEMORY` | `1024` |
| `--hyperv-static-macaddress` | `HYPERV_STATIC_MACADDRESS` | _undefined_ |
| `--hyperv-virtual-switch` | `HYPERV_VIRTUAL_SWITCH` | _first found_ |
| `--hyperv-vlan-id` | `HYPERV_VLAN_ID` | _undefined_ |
| `--hyperv-disable-dynamic-memory` | `HYPERV_DISABLE_DYNAMIC_MEMORY` | `false` |
## Example
## Example:
#### 1. Make sure Hyper-V is enabled
#### 1. Make sure Hyper-V is enabled.
Hyper-V is automatically enabled on a Docker for Windows install. To enable it manually, see [instructions on how to manually enable Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install) on the Microsoft developer network.
Hyper-V is automatically enabled on a Docker for Windows installation. To enable it manually, see [instructions on how to manually enable Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install) on the Microsoft developer network.
#### 2. Set up a new external network switch (Optional)
> **Note**: If you already have an external network switch you can skip this setup and use that one.
> **Note**: If you already have an external network switch, skip this setup and use that one instead.
Make sure you have Ethernet connectivity while you are doing this.
Open the **Hyper-V Manager**. (On Windows 10, just search for the Hyper-V Manager in the search field in the lower left search field.)
Open the **Hyper-V Manager**. (On Windows 10, search for the Hyper-V Manager in the lower left search field.)
Select the Virtual Switch Manager in the right-side **Actions** panel.
Select the **Virtual Switch Manager** on the right-hand **Actions** panel.
![Hyper-V manager](../img/hyperv-manager.png)
Set up a new **external network switch** to use instead of DockerNAT network switch (for Moby), which is set up by default when you install Docker for Windows. (Or if you already have another network switch set up, you can use that one, but it must be an **external** switch.)
Set up a new **external network switch** to use instead of DockerNAT network switch (for Moby), which is set up by default when you install Docker for Windows. If you already have another network switch set up, use that one instead but make sure it is an **external** switch.)
For this example, we created a virtual switch called `Primary Virtual Switch`.
@ -77,29 +79,28 @@ For this example, we created a virtual switch called `Primary Virtual Switch`.
#### 3. Reboot
See [this issue on virtualbox: Hangs on Waiting for VM to start #986](https://github.com/docker/machine/issues/986).
See this issue on virtualbox: [Hangs on Waiting for VM to start #986](https://github.com/docker/machine/issues/986).
A reboot of your desktop system clears out any problems with the routing tables. Without a reboot first, `docker-machine create ...` might get hung up on `Waiting for VM to start`.
Reboot your desktop system to clear out any routing table problems. Without a reboot first, `docker-machine create ...` might get hung up on `Waiting for VM to start`.
#### 4. Create the nodes with Docker Machine and the Microsoft Hyper-V driver
* Start an "elevated" PowerShell with administrator privileges. To do this, search for PowerShell, right-click, and choose Run as administrator.
* Start an "elevated" PowerShell with administrator privileges. To do this, search for PowerShell, then right click and choose ***Run as administrator***.
* Run the `docker-machine create` commands to create machines.
For example, if you follow along with the [Swarm mode
tutorial](/engine/swarm/swarm-tutorial/index.md) which asks you to create [three
networked host
machines](/engine/swarm/swarm-tutorial/index.md#three-networked-host-machines),
networked host machines](/engine/swarm/swarm-tutorial/index.md#three-networked-host-machines),
you can create these swarm nodes: `manager1`, `worker1`, `worker2`.
* Use the Microsoft Hyper-V driver and reference the new virtual switch you created.
```shell
docker-machine create -d hyperv --hyperv-virtual-switch "<NameOfVirtualSwitch>" <nameOfNode>
docker-machine create -d hyperv --hyperv-virtual-switch <NameOfVirtualSwitch> <nameOfNode>
```
Here is an example of creating `manager1` node:
Here is an example of creating a `manager1` node:
```shell
PS C:\WINDOWS\system32> docker-machine create -d hyperv --hyperv-virtual-switch "Primary Virtual Switch" manager1
@ -138,10 +139,10 @@ you can create these swarm nodes: `manager1`, `worker1`, `worker2`.
## Where to go next
As a point of interest, the virtual machines you create with the
[`docker-machine create`](/machine/reference/create.md) command show up in the
As a point of interest, the virtual machines you create with
[`docker-machine create`](/machine/reference/create.md) show up in the
Hyper-V Manager under "Virtual Machines", but you need to manage them with
[`docker-machine`](/machine/reference/index.md) commands not through the Hyper-V
[`docker-machine`](/machine/reference/index.md) commands and not through the Hyper-V
Manager.
To get started using `docker-machine` commands, see these topics:

95
release-notes/docker-machine.md
View File

@ -5,18 +5,57 @@ keywords: release notes, machine
toc_max: 2
---
## 0.16.0 (2018-11-08)
### General
* Updated the default storage driver to `overlay2` for several systems.
* Improved error reporting for the `ssh` subcommand when using the `--native-ssh` flag.
### Drivers
`amazonec2`
* Improved handling of VPC errors.
`openstack`
* Machine removal no longer fails upon attempting to delete a nonexistent keypair.
## 0.15.0 (2018-06-12)
### General
* `docker-machine` can now be installed using `go install`.
* Docker Machine is now built with Go `1.10`.
* SSH connections now include a keep alive option. (docker/machine #4450)
### Drivers
`amazonec2`
* Updated default AMIs to mitigate Meltdown and Spectre.
* Added `--amazonec2-security-group-readonly` flag to prevent mutating security groups.
`exoscale`
* Updated driver to `v0.9.23`.
`hyperv`
* Fixed Hyper-V precreate issues. (docker/machine #4426)
* Added the ability to disable Hyper-V dynamic memory management during VM creation with `--hyperv-disable-dynamic-memory`.
`vmwarefusion`
* Improved shell checks (docker/machine #4491).
## 0.14.0 (2018-03-06)
### General
* Added `--client-certs` flag to the `docker-machine regenerate-certs` command.
* Improved OpenBSD support
* Improved OpenBSD support.
* Fixed a bug with `scp` commands issued from a Windows host.
* Enabled progress output by default for `scp` commands using `rsync`
* Added `--quiet` flag to `scp` to suppress progress output
* Machine now uses the `ss` command to detect connectivity when `netstat` is unavailable
* Added bash completion for `docker-machine mount`
* Improved provisioning resilience on Debian-based hosts
* Enabled progress output by default for `scp` commands using `rsync`.
* Added `--quiet` flag to `scp` to suppress progress output.
* Machine now uses the `ss` command to detect connectivity when `netstat` is unavailable.
* Added bash completion for `docker-machine mount`.
* Improved provisioning resilience on Debian-based hosts.
### Drivers
@ -36,14 +75,14 @@ toc_max: 2
* Added support for arbitrary disk size
`google`
* Enabled disk auto-deletion on newly created machines
* Enabled disk auto-deletion on newly created machines.
* Fixed a bug preventing the removal of a machine if it had already been removed remotely.
* Added support for fully qualified network and subnetwork names
* Added support for fully qualified network and subnetwork names.
`hyperv`
* Fixed potential cmdlet collision with VMWare powercli
* Fixed a bug with virtual switch selection
* Machine now correctly detects if the user is a Hyper-V administrator when using a localized version of Windows
* Fixed potential cmdlet collision with VMWare powercli.
* Fixed a bug with virtual switch selection.
* Machine now correctly detects if the user is a Hyper-V administrator when using a localized version of Windows.
`openstack`
* Added `--openstack-config-drive` flag
@ -54,17 +93,17 @@ toc_max: 2
* Added OpenBSD support
`vmwarefusion`
* Improved error detection and reporting when creating a new instance
* Improved error detection and reporting when creating a new instance.
`vmwarevsphere`
* Added `--vmwarevsphere-folder` flag
* Added `--vmwarevsphere-folder` flag.
## 0.13.0 (2017-10-12)
### General
- Added new `docker-machine mount` command for mounting machine directories over SSHFS
- Improved some logging messages
- Added new `docker-machine mount` command for mounting machine directories over SSHFS.
- Improved some logging messages.
- Fixed a bug with the `scp` command when using an identity file.
- Fixed a parsing error that caused the boot2docker ISO cache to malfunction, forcing a new download everytime.
@ -74,32 +113,32 @@ toc_max: 2
- `docker-machine rm` now also cleans up the associated storage account if it has no remaining storage containers.
- The creation process will no longer recreate the associated subnet if it already it exists.
- `exoscale`
- Updated driver
- Removed default `docker-machine` affinity group if no other affinity group was specified
- Updated driver.
- Removed default `docker-machine` affinity group if no other affinity group was specified.
- `virtualbox`
- Fixed a bug where the machine would sometimes be assigned an invalid IP address at creation time.
- `vmwaresphere`
- Added support for multiple networks
- Added support for multiple networks.
## 0.12.2 (2017-7-12)
### General
* The `scp` sub-command now allows to provide an optional `user@` to the address.
* Fixed bash completion on OS X
* Fixed bash completion on OS X.
### Drivers
* `amazonec2`
* Updated default AMIs to the latest version of Ubuntu 16.04 LTS
* Fixed a bug preventing proper machine removal
* Updated default AMIs to the latest version of Ubuntu 16.04 LTS.
* Fixed a bug preventing proper machine removal.
* `vmwarevsphere`
* Creating VMs on a DRS-enabled cluster should now work properly
* Fixed a bug that prevented provisioning
* Creating VMs on a DRS-enabled cluster should now work properly.
* Fixed a bug that prevented provisioning.
* `vmwarefusion`
* Fixed a bug that prevented provisioning
* Fixed a bug that prevented provisioning.
* `exoscale`
* Updated library
* Updated library.
## 0.12.1 (2017-6-30)
@ -111,15 +150,15 @@ toc_max: 2
### General
- Various bash completion improvements
- Bump Go to version 1.8.3
- Various bash completion improvements.
- Bump Go to version 1.8.3.
### Drivers
- `openstack`
- Enable `HTTP_PROXY`
- `digitalocean`
- Add support for tagging
- Add support for tagging.
- `virtualbox`
- Scope DHCP address range based on CIDR
- `generic`