New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[minikube-docker-daemon] Error response from daemon: client is newer than server #338

Closed
skukreti opened this Issue Jul 14, 2016 · 6 comments

Comments

Projects
None yet
5 participants
@skukreti

skukreti commented Jul 14, 2016

On attempting to run any docker command after setting the environment to use the default docker environment, I get the following error:

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

I understand that this means that the client (docker cli) version should match the server (minikube docker daemon) version. Does minikube have a "docker cli" or a command to upgrade the docker daemon on the minikube VM?

@dlorenc

This comment has been minimized.

Show comment
Hide comment
@dlorenc

dlorenc Jul 14, 2016

Contributor

Hey,

Sorry, minikube only currently supports 1.11.1 on the server, which is what is supported by Kubernetes 1.3. Depending on your platform you can grab the correct binary here:
https://docs.docker.com/engine/installation/binaries/

Contributor

dlorenc commented Jul 14, 2016

Hey,

Sorry, minikube only currently supports 1.11.1 on the server, which is what is supported by Kubernetes 1.3. Depending on your platform you can grab the correct binary here:
https://docs.docker.com/engine/installation/binaries/

@yissachar

This comment has been minimized.

Show comment
Hide comment
@yissachar

yissachar Jul 14, 2016

I've found DVM to be very helpful when you have multiple Docker environments on different versions (as you likely will when using Minikube). With DVM you can easily switch between client versions to match whatever server you want to communicate with.

yissachar commented Jul 14, 2016

I've found DVM to be very helpful when you have multiple Docker environments on different versions (as you likely will when using Minikube). With DVM you can easily switch between client versions to match whatever server you want to communicate with.

@dlorenc

This comment has been minimized.

Show comment
Hide comment
@dlorenc

dlorenc Jul 14, 2016

Contributor

Nice pointer @yissachar. We should add a pointer to our docs about this.

Contributor

dlorenc commented Jul 14, 2016

Nice pointer @yissachar. We should add a pointer to our docs about this.

@dlorenc

This comment has been minimized.

Show comment
Hide comment
@dlorenc

dlorenc Aug 19, 2016

Contributor

This should be mostly fixed with #475

Contributor

dlorenc commented Aug 19, 2016

This should be mostly fixed with #475

@dlorenc dlorenc closed this Aug 19, 2016

@Dishwasha

This comment has been minimized.

Show comment
Hide comment
@Dishwasha

Dishwasha Sep 4, 2016

You should be able to export DOCKER_API_VERSION=1.23 on your host. See https://docs.docker.com/engine/reference/commandline/cli/#/environment-variables.

Dishwasha commented Sep 4, 2016

You should be able to export DOCKER_API_VERSION=1.23 on your host. See https://docs.docker.com/engine/reference/commandline/cli/#/environment-variables.

@loxal

This comment has been minimized.

Show comment
Hide comment
@loxal

loxal Oct 5, 2016

@Dishwasha worked nice but what is the correct approach to fix this issue? Do I need to stop all containers and restart them to make sure that a new docker server version is running? What is if the client has version 1.666.breaking-api-change which might prevent from restarting a docker container?

loxal commented Oct 5, 2016

@Dishwasha worked nice but what is the correct approach to fix this issue? Do I need to stop all containers and restart them to make sure that a new docker server version is running? What is if the client has version 1.666.breaking-api-change which might prevent from restarting a docker container?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment