Machine: Why 'docker-machine create' uses latest-edge version?

[JYKeith123]

I'm using stable version of docker in windows 10 with hyper-v. It's officially 17.03.1-ce.
When I create new docker machine, it uses 17.05.0-ce for the new machine which is the latest edge version at the moment.
Is this bug? or intended?

I searched for using specific version when docker machine creates, but it seems there is no such feature.
https://github.com/docker/machine/issues/1702

[ulm0]

+1 to this, it would be really nice to be able to provision a specific docker version

[SvenDowideit]

Rancher uses the scripts in https://github.com/rancher/install-docker and the --engine-install-url docker-machine create parameter to do this now.

And from docker-machine v0.12, these scripts work for RancherOS and other distros too.

[ulm0]

@SvenDowideit Wow, great job, didn't know about it at all. Gonna give it a try asap.

[andrestc]

@SvenDowideit such a nice job, thanks for that. http://get.docker.com should support something like that.

[mahnunchik]

Hi All,

https://get.docker.com/ installs from edge repository, not from stable.

[lostllama]

@mahnunchik So what is the stable repository URL? Even the documentation example for --engine-install-url uses http://get.docker.com.

[christianbundy]

@lostllama Sounds like Docker's official position is that https://get.docker.com shouldn't be used for production use, which makes it confusing that it's used in Machine.

[ghisvail]

nvidia-docker supports the stable channel only. As a result, it's not possible to use docker machine to instantiate a node with docker + nvidia-docker without resorting to downgrading docker to the stable version manually.

Instead, it would be nice to have some sort of flag to leave the choice between deploying Docker from the edge (default) or a stable channel.