docker-machine inside Docker for Mac should be updated to at least 0.12.1

[twang2218]

docker-machine 0.12.0 has a serious issue:

docker/machine#4156
docker/machine#4166
docker/machine#4189
docker/machine#4197
docker/machine#4198

People cannot use the command to create a docker host. The issue has been fixed in 0.12.1, and actually, the 0.12.2 has been released for a while. However, the version of docker-machine inside Docker for Mac is still 0.12.0.

Please update the version of docker-machine to the latest version. Thanks.

[brandontamm]

I am not sure that this issue has been fixed in v0.12.2 - see my most recent tests with v0.12.2: docker/machine#4189

[dougtoppin]

I posted that I was having the same issue with v0.12.1 and then realized that there was a v0.12.2.
I just tried that using my mac and it did work without any problem.

docker-machine --version
docker-machine version 0.12.2, build 9371605

docker-machine create --driver amazonec2 --amazonec2-vpc-id vpc-xxx --amazonec2-zone e aws-test
...
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: docker-machine env aws-test

[drujensen]

For those looking for a work-around:

brew install docker-machine
brew link --overwrite docker-machine

[twang2218]

Any updates on this issue? I'm currently using the workaround @drujensen mentioned above, however, Docker for Mac often overwrote the /usr/local/bin/docker-machine with the outdated version, which caused many trouble.

Could any one here in the Docker for Mac team update the docker-machine to the latest version? Big thanks.

[drujensen]

Even though the version has been updated to v0.12.2 build 0371605 in docker for mac, docker-machine does not properly work and behaves similar to v0.12.0.

However, the brew version v0.12.2 build 0371605 is stable.

For example, when performing a docker-machine ls using the version with docker for mac, I get Timeout errors. However, when I replace it using the brew docker-machine, there are no Timeout errors.

$docker-machine -v
docker-machine version 0.12.2, build 9371605

$ls -al /usr/local/bin/docker-machine 
lrwxr-xr-x  1 drujensen  staff  77 Sep 13 08:46 /usr/local/bin/docker-machine -> /Users/drujensen/Library/Group Containers/group.com.docker/bin/docker-machine

$docker-machine ls
NAME                     ACTIVE   DRIVER      STATE     URL                        SWARM   DOCKER        ERRORS
catalyst-elk                      amazonec2   Timeout                                                    
catalyst-prod-0.34.2-1            amazonec2   Timeout                                                    
catalyst-prod-0.34.2-2            amazonec2   Timeout                                                    
catalyst-qa-latest-1     -        amazonec2   Running   {ip address}           v17.06.1-ce   
catalyst-sentry                   amazonec2   Timeout                                                    

$brew unlink docker-machine
Unlinking /usr/local/Cellar/docker-machine/0.12.2... 4 symlinks removed

$brew link --overwrite docker-machine
Linking /usr/local/Cellar/docker-machine/0.12.2... 5 symlinks created

$docker-machine -v
docker-machine version 0.12.2, build 9371605

$ls -al /usr/local/bin/docker-machine 
lrwxr-xr-x  1 drujensen  admin  50 Sep 13 08:33 /usr/local/bin/docker-machine -> ../Cellar/docker-machine/0.12.2/bin/docker-machine

$docker-machine ls
NAME                     ACTIVE   DRIVER      STATE     URL                        SWARM   DOCKER        ERRORS
catalyst-elk             -        amazonec2   Running   {ip address}           v17.07.0-ce   
catalyst-prod-0.34.2-1   -        amazonec2   Running   {ip address}           v17.07.0-ce   
catalyst-prod-0.34.2-2   -        amazonec2   Running   {ip address}           v17.07.0-ce   
catalyst-qa-latest-1     -        amazonec2   Running   {ip address}           v17.06.1-ce   
catalyst-sentry          -        amazonec2   Running   {ip address}           v17.07.0-ce   

[twang2218]

@drujensen Good observation, I thought they should be identical binaries, obviously, it's not the case.
But, I think it's a different issue, I'm going to close this issue as it's been updated to the 0.12.2 already. Could you open another issue to target the different behavior problem? Thanks.

[drujensen]

@twang2218 ok, opened a new issue #2055

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked