boot2docker upgrade should warn if the cli is outdated

[proppy]

It would be nice if boot2docker upgrade warned you that a new version of the cli is available and that you should update your binary.

For the 1.2->1.3 transition, if you do:

boot2docker upgrade
$(boot2docker shellinit)
# Writing /home/proppy/.docker/boot2docker-vm/ca.pem:
# Writing /home/proppy/.docker/boot2docker-vm/cert.pem:
# Writing /home/proppy/.docker/boot2docker-vm/key.pem:
#    export DOCKER_HOST=tcp://192.168.59.103:2376
#    export DOCKER_CERT_PATH=/home/proppy/.docker/boot2docker-vm
docker version

It will fails with:

$ docker version
Client version: 1.3.0
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): c78088f
OS/Arch (client): linux/amd64
2014/10/16 18:33:03 Get http://192.168.59.103:2376/v1.15/version: malformed HTTP response "\x15\x03\x01\x00\x02\x02"

Because DOCKER_TLS_VERIFY is not set

[prologic]

Also side not for fig users; Do: pip install git+https://github.com/docker/fig.git#egg=fig to get the unreleased 1.x version of fig that works with Docker 1.3.x :)

[proppy]

Maybe a good solution to this kind of issue would be to have shellinit retreive the needed env vars over ssh. That way the .iso could expose the env needed to connect to the daemon according the new flavor of default --flags of the day.

[SvenDowideit]

see #242 - which should upgrade all 3 artifacts for 1.4

I do like the idea that docker host get the info from the b2d host where possible too.

[tianon]

@proppy can you confirm that #242 fixed this issue for you?

[tianon]

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).