title: Starting minikube in a Linux box requires authentication with Google Container Registry, why?
body: <p>I am currently learning Kubernetes and I am playing with minikube tool. I have decided to install the tool in a VirtualBox instance that runs ubuntu/xenial64. I have created this instance using Vagrant and connected the instance through ssh.
  I have installed minikube in accordance to the tool documentation - <a href="https://minikube.sigs.k8s.io/docs/start/" rel="nofollow noreferrer">https://minikube.sigs.k8s.io/docs/start/</a>.
  When I run:
  <code>$ minikube start</code>,
  it failed with the following message:</p>
  
  <pre><code>$ minikube start
    minikube v1.11.0 on Ubuntu 16.04 (vbox/amd64)
  ✨  Using the docker driver based on existing profile
    Starting control plane node minikube in cluster minikube
    Pulling base image ...
    Unfortunately, could not download the base image gcr.io/k8s-minikube/kicbase:v0.0.10 
  ❗  In order to use the fall back image, you need to log in to the github packages registry
    Please visit the following link for documentation around this: 
      https://help.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages#authenticating-to-github-packages
  
    Please either authenticate to the registry or use --base-image flag to use a different registry.
  </code></pre>
  
  <p>For some reason, in order to download minikube base image, it requires to authenticate to the gcr.io registry (Google Container Registry). The minikube documentation does mention nothing about this requirement. I am wondering why it happened. My understanding is it should not be mandatory to have a gsr account in order to use minikube. What am I doing wrong?
  And what is the kicbase container (KIC) that minikube depends on?
  I appreciate any help on this problem. Thank you. </p>