You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
On Tue, May 28, 2019, 12:24 PM Anders Björklund ***@***.***> wrote:
The suggestion was to just delete the environment variable, the daemon
will handle the API negotation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4363?email_source=notifications&email_token=AAAYYMHYB7YMAUI5CO3ESVDPXWBHVA5CNFSM4HQF23GKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWNFNYY#issuecomment-496654051>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAYYMB2MKX7WIOTWZLYVITPXWBHVANCNFSM4HQF23GA>
.
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
The text was updated successfully, but these errors were encountered: