-
Notifications
You must be signed in to change notification settings - Fork 1.3k
race condition: boot2docker upgrade
after docker release but before boot2docker release results in client server version mismatch
#731
Comments
Loosely related to #575 . |
@jokeyrhyme Hm, this should not happen. Sorry to hear. It sounds like the new boot2docker ISO has not been downloaded (it should be). Could you please paste the output from when you run the
I love it when a plan comes together! |
@nathanleclaire eek. Too late now. boot2docker 1.5.0 is out now, so this exact situation is no longer repeatable. These are the prerequisites in order to reproduce:
|
Ah, so here's our issue. It's a race between the releases - probably should have an additional check around that. Thanks for reporting! |
hi Nathan, i am facing the similar issue. So what is the fix? Could you please help me with that? Regards, |
@aravindgan |
it does not work, sudo boot2docker upgrade To connect the Docker client to the Docker daemon, please set: bash-3.2$ docker version |
how can i manually downgrade to older version of client? can you help me with the steps? |
@aravindgan You can find a binary named However, the issue you're running into shouldn't happen. Could you please share the contents of the file Also, I don't think this is the issue at hand, but you shouldn't need Lastly, please ensure that your environment variables are set correctly ( |
before you run |
Download the docker windows client from here https://master.dockerproject.com/windows/amd64/docker-1.4.1-dev.exe which has api version 1.16 |
I just encountered the same error. I had v1.4.1 installed and working. I just upgraded using the v1.5.0 release and upon running boot2docker.app, I received the error:
Running |
boot2docker upgrade
results in client server version mismatchboot2docker upgrade
after docker update but before boot2docker update results in client server version mismatch
boot2docker upgrade
after docker update but before boot2docker update results in client server version mismatchboot2docker upgrade
after docker release but before boot2docker release results in client server version mismatch
Hi, I am having the same issue. I am running docker on Fedora 20 and I am experimenting on swarm with docker. I am able to configure swarm but can't use it. [peeyush@localhost swarm]$ docker-machine_linux-amd64 ls [peeyush@localhost swarm]$ docker version And solution? because seems like I can't do boot2docker upgrade! |
@Pensu are you able to install just the 1.5.0 stable client? The output says you are running 1.5.0-dev. |
@jokeyrhyme I tried to do sudo yum update docker, but it's still 1.4.1, not sure how to get stable 1.5.0 for Fedora 20. Right now I am just building it from git code. |
@Pensu building from git code is fine, but make sure that you've checked out a stable tag. Don't just build from master (unless you know that works). |
@jokeyrhyme okay, that might be the issue, let me switch to the stable branch and try it out again. Thanks :) |
@jokeyrhyme Thanks for the advice and finally I am not getting that error. But I am not able to see my nodes in docker info in swarm master env. [peeyush@localhost swarm]$ docker-machine_linux-amd64 ls [peeyush@localhost swarm_demo]$ eval "$(docker-machine_linux-amd64 env swarm-master)" It's not showing me the info about the node that I added i.e. swarm-node-00. Is there any other API or something or my setup still has something wrong? Update: Okay, got it. I also have to use --swarm while loading the environment. |
@Pensu all I can suggest is double-checking how you've set it up: https://docs.docker.com/machine/#using-docker-machine-with-docker-swarm |
Same issue. Downloaded and installed boot2docker dmg file just now and encountered this when opening boot2docker:
running boot2docker upgrade from Mac terminal (not boot2docker) solved it for me. |
How the boot2docker maintainers decide to tackle this is their business, but I'm personally happy when |
I'm using docker-machine and had the same error, docker-machine upgrade fixed the problem. |
|
Do this:
|
@jayasimhan I do as your method, and success.Thanks :) |
I just had to stop VM and rerun upgrade and it works. |
I just had a problem where client version was 1.18 and server version was 1.17
Running |
It has been well-established that once all the required versions of docker and boot2docker are actually available, that simply running |
I've just had the same issue after |
If you installed docker directly on native OS instead of VM, you need to restart the docker daemon service to remove this issue, e.g. using the following command in ubuntu: sudo service docker restart. |
I got this today, but running |
👍 Verifying that |
I wonder if this is still an issue; I think the releases are now better coordinated, for example, Boot2Docker 1.7.0-rc3 was available 6 minutes after Docker 1.7.0-rc3; moby/moby#13528 (comment). |
@thaJeztah I've noticed this too. Why keep this as a code problem if the deployment process has solved it? |
This does not appear to me to be solved. Following the official installation instructions for Windows (just now) results in This is for the current stable version of Docker, 1.6.2. Running |
Still an issue when docker is released before boot2docker is released. Currently (2015-06-18 7pm GMT) docker 1.7 is released but boot2docker is only available in 1.6.2. Doing a Is it an alternative to restrict Regards, Leif |
@leifhanack are you sure? 1.7 was released an hour ago; https://github.com/boot2docker/boot2docker/releases |
I have had the luck of upgrading in the hour right between the two releases:) |
@leifhanack that's unfortunate, @tianon missed the GitHub notification that 1.7 was merged, resulting in a slight delay, so I pinged him on IRC, apologies for the inconvenience there. |
It also takes time to actually build these things -- they're not
instantaneous. 😄
|
@thaJeztah @tianon no problem at all. thanks for all your work! btw since 1.7 I have a certificate issue.
so far I couldn't find sth related here thanks a lot, leif |
when i remove my vm ( |
I can report the same issue as @leifhanack. It is solved by |
Am I the only one who finds the messages confusing? ❯ brew install codeclimate 12:39:30 PM
==> Installing codeclimate from codeclimate/homebrew-formulae
==> Downloading https://github.com/codeclimate/codeclimate/archive/v0.0.7.tar.gz
==> Downloading from https://codeload.github.com/codeclimate/codeclimate/tar.gz/v0.0.7
######################################################################## 100.0%
==> env PATH=/usr/local/bin:/usr/local/Library/ENV/4.3:/usr/bin:/bin:/usr/sbin:/sbin PREFIX=/usr/local/Cellar/codecl
bin/check Notice the version numbers carefully. Those specific versions (1.19, 1.18) are only ever mentioned in the error from the daemon.
Now this next one is the kicker. If boot2docker is up to date, then why is it downloading a new image of the same version?
|
@kevinSuttle I opened #670 a while back RE: unnecessary downloads |
Hi folks, |
@glaucio-melo-movile it's possible you somehow only updated your client, but not the virtual machine; this doesn't sound like the "race" described here, because docker 1.8.x has been available for a while (and so is boot2docker with docker 1.8.x) Try updating the VM by running |
@kevinSuttle you are definitely not the only one — the entire process is a living nightmare. it's like we resurrected the worst of linux sysadmin circa 1999. |
Just ran
boot2docker upgrade
after the Docker 1.5.0 release but before the matching boot2docker release. So I was on boot2docker 1.4.1.The upgrade process updated my docker binary to 1.5.0, but kept the boot2docker parts at 1.4.1, which is as expected.
Unfortunately, I now get the following output from `docker version:
And the following error for many docker commands:
I noticed that the old docker binary is backed up to ~/.boot2docker, so this is not the end of the world for me or anything. :)
I wonder if it's possible for
boot2docker upgrade
to check the API versions and automatically rollback if there is a mismatch? Or maybe somehow know that there will be a mismatch in advance? /shrugUpdate: It has been well-established that once all the required versions of docker and boot2docker are actually available, that simply running
boot2docker upgrade
is sufficient to correct any issues. When I first reported this issue, my desire was thatboot2docker upgrade
should not be able to break anything in the first place. Running it a second time a few days later is known to fix it, but is little consolation if you are prevented from using Docker during this time.The text was updated successfully, but these errors were encountered: