search

docker / machine

Machine management for a container-centric world
https://docs.docker.com/machine/
Apache License 2.0
6.63k stars 1.97k forks source link

machine upgrade does not upgrade vmwarevsphere #3005

Open oxypwn opened 8 years ago

oxypwn commented 8 years ago

machine upgrade machines using the vmwarevsphere driver seems to fail without errors.

docker-machine version 0.6.0, build e27fb87

mbp scripts → machine upgrade d
Waiting for SSH to be available...
Detecting the provisioner...
Upgrading docker...
Stopping machine to do the upgrade...
Upgrading machine "d"...
No default Boot2Docker ISO found locally, downloading the latest release...
Latest release for github.com/boot2docker/boot2docker is v1.10.0
Downloading /Users/paul/.docker/machine/cache/boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v1.10.0/boot2docker.iso...
0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
Copying /Users/paul/.docker/machine/cache/boot2docker.iso to /Users/paul/.docker/machine/machines/d/boot2docker.iso...
Starting machine back up...
(d) Waiting for VMware Tools to come online...
Restarting docker...
mbp scripts → machine ls
NAME      ACTIVE   DRIVER          STATE     URL                           SWARM   DOCKER    ERRORS
d         -        vmwarevsphere   Running   tcp://192.168.88.96:2376              v1.9.1
nathanleclaire commented 8 years ago

cc @frapposelli

pskiwi commented 8 years ago

Manually (via vSphere-client) replacing the boot2docker.iso in the vm-datastore seems to resolve the problem.

frapposelli commented 8 years ago

definitely a bug, I'll look into it, thanks for reporting.

nathanleclaire commented 8 years ago

Any update on this @frapposelli ?

philipz commented 8 years ago

I also have this problem.

➜  ~ docker-machine -v
docker-machine version 0.7.0, build a650a40
➜  ~ docker-machine ls
NAME      ACTIVE   DRIVER          STATE     URL                        SWARM   DOCKER    ERRORS
node-00   -        vmwarevsphere   Running   tcp://192.168.2.208:2376           v1.10.2   
node-01   -        vmwarevsphere   Running   tcp://192.168.2.29:2376            v1.10.2   
node-02   -        vmwarevsphere   Running   tcp://192.168.2.87:2376            v1.10.2   
➜  ~ docker-machine upgrade node-00
Waiting for SSH to be available...
Detecting the provisioner...
Upgrading docker...
Stopping machine to do the upgrade...
Upgrading machine "node-00"...
Default Boot2Docker ISO is out-of-date, downloading the latest release...
Latest release for github.com/boot2docker/boot2docker is v1.11.1
Downloading /home/philipz/.docker/machine/cache/boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v1.11.1/boot2docker.iso...
0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
Copying /home/philipz/.docker/machine/cache/boot2docker.iso to /home/philipz/.docker/machine/machines/node-00/boot2docker.iso...
Starting machine back up...
(node-00) Waiting for VMware Tools to come online...
Restarting docker...
➜  ~ docker-machine ls             
NAME      ACTIVE   DRIVER          STATE     URL                        SWARM   DOCKER    ERRORS
node-00   -        vmwarevsphere   Running   tcp://192.168.2.208:2376           v1.10.2   
node-01   -        vmwarevsphere   Running   tcp://192.168.2.29:2376            v1.10.2   
node-02   -        vmwarevsphere   Running   tcp://192.168.2.87:2376            v1.10.2
sitle commented 8 years ago

I actually have the same bug while trying to upgrade from 1.11.1 to 1.12 with vsphere : 

$ docker-machine upgrade docker01
Waiting for SSH to be available...
Detecting the provisioner...
Upgrading docker...
Stopping machine to do the upgrade...
Upgrading machine "docker01"...
Copying /Users/sitle/.docker/machine/cache/boot2docker.iso to /Users/sitle/.docker/machine/machines/docker01/boot2docker.iso...
Starting machine back up...
(docker01) Waiting for VMware Tools to come online...
Restarting docker...

then

$ eval $(docker-machine env docker01)
$ docker ps
Error response from daemon: client is newer than server (client API version: 1.24, server API version: 1.23)

I actually use this workaround for now to make it work : 

$ export DOCKER_API_VERSION=1.23
$ docker ps
axot commented 8 years ago

I have the same issue, always replace boot2docker.iso manually, any official methods?

StalkAlex commented 7 years ago

More then a year and still not fixed?