Skip to content
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

DOCKER_API_VERSION does not match version in VM image #4363

Closed
tstromberg opened this issue May 28, 2019 · 3 comments · Fixed by #4364
Closed

DOCKER_API_VERSION does not match version in VM image #4363

tstromberg opened this issue May 28, 2019 · 3 comments · Fixed by #4364
Assignees
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@tstromberg
Copy link
Contributor

tstromberg commented May 28, 2019

Currently we hardcode DOCKER_API_VERSION show to users who run minikube docker-env.

If a user starts an older VM image, we incorrectly advertise the DOCKER_API_VERSION it supports. We shouldn't hardcode the value.

The workaround we recommend at the moment is that users run minikube delete in order to create a newer VM version. We may also want to warn users if they start minikube from a VM where the Docker version is older than expected.

See related Skaffold bug: GoogleContainerTools/skaffold#2187

The error users notice is:

docker build: Error response from daemon: client version 1.39 is too new. Maximum supported API version is 1.38

@tstromberg tstromberg added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 28, 2019
@tstromberg tstromberg changed the title docker-env DOCKER_API_VERSION does not match version in VM image DOCKER_API_VERSION does not match version in VM image May 28, 2019
@afbjorklund
Copy link
Collaborator

The suggestion was to just delete the environment variable, the daemon will handle the API negotation.

@tstromberg
Copy link
Contributor Author

tstromberg commented May 28, 2019 via email

@tstromberg
Copy link
Contributor Author

Related: minishift/minishift#1655

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants