minikube: docker: error getting ip during provisioning: IPs output should only be one line, got 2 lines
Steps to reproduce the issue:
- After install minikube following this link https://kubernetes.io/docs/tasks/tools/install-minikube/
- Then execute
minikube start --driver=docker, then error above shown.
😄 minikube v1.11.0 on Ubuntu 20.04
✨ Using the docker driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🏃 Updating the running docker "minikube" container ...
🤦 StartHost failed, but will try again: provision: Temporary Error: error getting ip during provisioning: IPs output should only be one line, got 2 lines
🏃 Updating the running docker "minikube" container ...
😿 Failed to start docker container. "minikube start" may fix it: provision: Temporary Error: error getting ip during provisioning: IPs output should only be one line, got 2 lines
💣 error provisioning host: Failed to start host: provision: Temporary Error: error getting ip during provisioning: IPs output should only be one line, got 2 lines
😿 minikube is exiting due to an error. If the above message is not useful, open an issue:
👉 https://github.com/kubernetes/minikube/issues/new/choose
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 19 (3 by maintainers)
I also had this error. I believe it is because on the system I am using, docker commands have to be run with
sudo. This meant the config file was owned by root. I did not need to delete the config file to get minikube to start, just make it readable:chmod 777 ~/.dockerchmod 66 ~/.docker/config.jsonI also had this problem , but on MacOs system.First I thought there was a problem about proxy, but after using
minikube deletemany times, I saw a message ‘WARNING: Error loading config file: ~/.docker/config.json: EOF’ . then I deleted this file byrm ~/.docker/config.jsonand thenminikube deleteand then start minikube again and it’s going OK.I had the same problem and first I tried to remove the .docker/config.json file, the same issue persists. So:
After deleted the config.json file I tried these steps:
$ sudo chown “$USER”:“$USER” /home/“$USER”/.docker -R $ sudo chmod g+rwx “$HOME/.docker” -R
Change user for your whoami, try whoami in your terminal and paste the result on $USER and be happy!
Yes that worked.
Am currently facing this issue too.
Hey @phua-gingsheng could you provide the output of: