minikube: Failed to cache ISO: open .netrc: permission denied

I just freshly installed minikube to try it out in my Mac but have not managed to start

stanleynguyen@macair:~ $ minikube version
minikube version: v1.4.0
commit: 7969c25a98a018b94ea87d949350f3271e9d64b6
stanleynguyen@macair:~ $ minikube start
πŸ˜„  minikube v1.4.0 on Darwin 10.14.6
πŸ’Ώ  Downloading VM boot image ...

πŸ’£  Failed to cache ISO: https://storage.googleapis.com/minikube/iso/minikube-v1.4.0.iso: invalid checksum: Error downloading checksum file: Error parsing netrc file at "/Users/stanleynguyen/.netrc": open /Users/stanleynguyen/.netrc: permission denied

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
πŸ‘‰  https://github.com/kubernetes/minikube/issues/new/choose

It seems that because minikube is asking for access to my .netrc file but I don’t think it’s supposed to have access to such file with sensitive info like my passwords

I still tried running it in superuser mode anyway, and faced with another problem

stanleynguyen@macair:~ $ sudo minikube start
Password:
πŸ˜„  minikube v1.4.0 on Darwin 10.14.6
πŸ›‘  The "virtualbox" driver should not be used with root privileges.
πŸ’‘  If you are running minikube within a VM, consider using --vm-driver=none:
πŸ“˜    https://minikube.sigs.k8s.io/docs/reference/drivers/none/

Note: I have virtualbox installed in my local as VM environment (I also used this for Docker)

The operating system version: MacOS Mojave 10.14.6

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 20 (5 by maintainers)

Most upvoted comments

It seems like the network library minikube uses accesses .netrc, and raises an error if it cannot: https://github.com/hashicorp/go-getter/blob/master/netrc.go

As a workaround, you can manually download the ISO:

curl -L https://storage.googleapis.com/minikube/iso/minikube-v1.4.0.iso > ~/.minikube/cache/iso/minikube-v1.4.0.iso

Like most network commands, curl also references your .netrc, but it is nice enough to fail.

Did you open a bug report upstream yet ? Looks like a library issue…