Closed bbakersmith closed 6 years ago
I hunted down the binary storage location: https://storage.googleapis.com/minikube
I see that the v1.8.0 binary was indeed modified on November 30
<Contents>
<Key>k8sReleases/v1.8.0/localkube-linux-amd64</Key>
<Generation>1512063866146054</Generation>
<MetaGeneration>1</MetaGeneration>
<LastModified>2017-11-30T17:44:26.081Z</LastModified>
<ETag>"56630c50366efa492d36d0b885ee7d3d"</ETag>
<Size>155452040</Size>
</Contents>
Sorry about this.
Yes, this was due to a breaking api change we introduced in 0.24.0 for localkube.
You can either
Obviously its pretty bad to overwrite binaries, but we needed to do so to not break future versions since we found this issue after we had released 0.24.0. We're in a odd in-between state before we fully deprecate localkube, and the transition could have been a little cleaner, but we haven't had the bandwidth.
Thanks for the prompt reply! Upgrading to 0.24.1 fixed the issue.
Environment:
Minikube version: v0.23.0
What happened:
I installed Minikube and it worked. 2 weeks later I installed Minikube on a new machine (identical hardware and OS) and the system containers failed due to a TLS handshake error. All the tool versions and cached image names in ~/.minikube/cache are the same between both machines.
What you expected to happen:
I expect Minikube to run on both machines given the same versions of all software and images.
How to reproduce it:
From a fresh install with no ~/.minikube directory today:
The dashboard never comes up, TLS errors show up in the logs as the system containers rebuild forever.
If I copy an older version of localkube-v1.8.0 (same name and version but from November 21) into ~/.minikube/cache/localkube and
Everything works.
So, something changed in localkube-v1.8.0 between November 21 and today that breaks minikube. Diffing the older and newer binaries confirms that they did change. This should not happen, versioned binaries should be immutable.
This behavior has been confirmed on multiple laptops.
Output of
minikube logs
(if applicable):Additional Questions: