Problem

When an Instance is created its is placed in the VPC associated with the Subnet and Security Group and not the VPC passed on the command line, e.g.

docker-machine -D create -d amazonec2 --amazonec2-vpc-id alvin-dockercon --amazonec2-subnet-id subnet-26df460d --amazonec2-security-group alvin-test-sg2 foo

Reproduce

1. Create vpc1 and vpc2
2. Create Security Groups
   • sg1 associated with vpc1
   • sg2 associated with vpc2
3. Create Subnets
   • sn1 associated with vpc1
   • sn2 associated with vpc2

$ docker-machine -D create -d amazonec2 --amazonec2-vpc-id vpc1 --amazonec2-subnet-id <id of sn2> --amazonec2-security-group sg2 foo

Solution

Validate that the VPC chosen is a match for the VPC passed on the command line and either

• WARN that these differ and which VPC was chosen
• ERR that they do not match

Environment

uname -a
Darwin vero.local 14.4.0 Darwin Kernel Version 14.4.0: Thu May 28 11:35:04 PDT 2015; root:xnu-2782.30.5~1/RELEASE_X86_64 x86_64

docker-machine --version
docker-machine version 0.3.0 (0a251fe)