Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Failed to enable container runtime: docker restart failed (insecure registry ... invalid host) #3800

Closed
Freddixx opened this issue Mar 5, 2019 · 10 comments
Closed

Failed to enable container runtime: docker restart failed (insecure registry ... invalid host) #3800

Freddixx opened this issue Mar 5, 2019 · 10 comments
Labels
co/docker-env docker-env issues co/virtualbox priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@Freddixx
Copy link

Freddixx commented Mar 5, 2019

This error started occurring after I updated minikube to the latest version today. Essentially after setting up a new cluster, minikube tries to restart docker with systemctl which is not available on macos:

minikube start --vm-driver=virtualbox

Full output:

😄  minikube v0.34.1 on darwin (amd64)
💡  Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
🏃  Re-using the currently running virtualbox VM for "minikube" ...
⌛  Waiting for SSH access ...
📶  "minikube" IP address is 192.168.99.100
🐳  Configuring Docker as the container runtime ...
💣  Failed to enable container runtime: command failed: sudo systemctl restart docker
stdout: 
stderr: Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
: Process exited with status 1

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

Running on:

image

I am not sure if this is a known issue - any help is appreciated :)

P.S.: Not that I think I would have any impact, but I tried both hyperkit and virtualbox drivers.
@afbjorklund
Copy link
Collaborator

The command is run over ssh, to the virtualbox VM started. Not on the host (the Mac).

If you could run minikube ssh and run those commands, they might have more input:

See "systemctl status docker.service" and "journalctl -xe" for details.

According to your output it looks like you are trying to upgrade an old VM, maybe that is it.

@Freddixx
Copy link
Author

Freddixx commented Mar 6, 2019

Hi @afbjorklund, thanks for the quick response!

According to your output it looks like you are trying to upgrade an old VM, maybe that is it.

I ran minikube delete before each of my attempts. So I hope that is not it. Or is that not enough to ensure it's a fresh VM?

I will run those if I have a free minute and post the output!

@Freddixx
Copy link
Author

Freddixx commented Mar 6, 2019

Here are the outputs:

$ systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-03-06 08:58:38 UTC; 22s ago
     Docs: https://docs.docker.com
  Process: 2820 ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --tlskey /etc/docker/server-key.pem --label provider=virtualbox --insecure-registry 10.96.0.0/12 --insecure-registry eu.gcr.io/goeuro-dev (code=exited, status=1/FAILURE)
 Main PID: 2820 (code=exited, status=1/FAILURE)

Mar 06 08:58:38 minikube systemd[1]: Starting Docker Application Container Engine...
Mar 06 08:58:38 minikube systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Mar 06 08:58:38 minikube systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 06 08:58:38 minikube systemd[1]: Failed to start Docker Application Container Engine.

And:

Mar 06 08:58:36 minikube VBoxService[2045]: 00:11:10.232971 timesync vgsvcTimeSyncWorker: Radical host time change: 32 600 665 000 000ns (HostNow=1 551 862 716 953 000 000 ns HostLast=1 551 830 116 288 000 000 ns)
Mar 06 08:58:36 minikube kernel: 00:11:10.232971 timesync vgsvcTimeSyncWorker: Radical host time change: 32 600 665 000 000ns (HostNow=1 551 862 716 953 000 000 ns HostLast=1 551 830 116 288 000 000 ns)
Mar 06 08:58:36 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57950 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:36 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57951 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57952 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57953 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57954 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57955 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57956 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57957 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube kernel: hpet1: lost 314 rtc interrupts
Mar 06 08:58:37 minikube sudo[2694]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/hostname minikube
Mar 06 08:58:37 minikube sudo[2696]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/tee /etc/hostname
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57958 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57959 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57960 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57961 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57962 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sudo[2715]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/rm -f /etc/docker/ca.pem
Mar 06 08:58:37 minikube sudo[2716]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/mkdir -p /etc/docker
Mar 06 08:58:37 minikube sudo[2717]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/scp -t /etc/docker
Mar 06 08:58:37 minikube sudo[2718]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/rm -f /etc/docker/server.pem
Mar 06 08:58:37 minikube sudo[2719]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/mkdir -p /etc/docker
Mar 06 08:58:37 minikube sudo[2720]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/scp -t /etc/docker
Mar 06 08:58:37 minikube sudo[2721]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/rm -f /etc/docker/server-key.pem
Mar 06 08:58:37 minikube sudo[2722]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/mkdir -p /etc/docker
Mar 06 08:58:37 minikube sudo[2723]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/scp -t /etc/docker
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57963 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57964 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sudo[2731]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/mkdir -p /lib/systemd/system
Mar 06 08:58:37 minikube sudo[2733]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/tee /lib/systemd/system/docker.service
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57965 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57966 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sudo[2742]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/mkdir -p /etc/sysconfig
Mar 06 08:58:37 minikube sudo[2744]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/tee /etc/sysconfig/crio.minikube
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57967 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57968 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sudo[2751]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/systemctl daemon-reload
Mar 06 08:58:37 minikube systemd[1]: Reloading.
Mar 06 08:58:37 minikube systemd-fstab-generator[2755]: Ignoring "noauto" for root device
Mar 06 08:58:37 minikube systemd[1]: Configuration file /usr/lib/systemd/system/containerd.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Mar 06 08:58:37 minikube systemd[1]: Starting Garbage Collection for rkt...
-- Subject: Unit rkt-gc.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit rkt-gc.service has begun starting up.
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57969 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube systemd[1]: Started Garbage Collection for rkt.
-- Subject: Unit rkt-gc.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--       
-- Unit rkt-gc.service has finished starting up.
-- 
-- The start-up result is RESULT.
Mar 06 08:58:37 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57970 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:37 minikube sudo[2775]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/systemctl -f restart crio
Mar 06 08:58:37 minikube systemd[1]: Starting Open Container Initiative Daemon...
-- Subject: Unit crio.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit crio.service has begun starting up.
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06T08:58:37Z" level=warning msg="DefaultWorkloadTrust deprecated
Mar 06 08:58:37 minikube crio[2776]: /*\ Warning /*\
Mar 06 08:58:37 minikube crio[2776]: DEPRECATED: Use Runtimes instead.
Mar 06 08:58:37 minikube crio[2776]: The support of this option will continue through versions 1.12 and 1.13. By
Mar 06 08:58:37 minikube crio[2776]: version 1.14, this option will no longer exist.
Mar 06 08:58:37 minikube crio[2776]: /*\ Warning /*\
Mar 06 08:58:37 minikube crio[2776]: "
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06T08:58:37Z" level=warning msg="runtime is deprecated in favor of runtimes, please switch to that"
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06 08:58:37.940175278Z" level=debug msg="[graphdriver] trying provided driver "overlay""
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06 08:58:37.978670858Z" level=debug msg="overlay test mount with multiple lowers succeeded"
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06 08:58:37.993502367Z" level=debug msg="backingFs=extfs, projectQuotaSupported=false, useNativeDiff=true"
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06 08:58:37.993848562Z" level=warning msg="implicit hook directories are deprecated; set --hooks-dir="/usr/share/containers/oci/hooks.d" explicitly to continue to load hooks from this directory"
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06 08:58:37.993931150Z" level=warning msg="implicit hook directories are deprecated; set --hooks-dir="/etc/containers/oci/hooks.d" explicitly to continue to load hooks from this directory"
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06 08:58:37.993982803Z" level=debug msg="reading hooks from /usr/share/containers/oci/hooks.d"
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06 08:58:37.994038372Z" level=debug msg="reading hooks from /etc/containers/oci/hooks.d"
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06 08:58:37.994643547Z" level=error msg="error updating cni config: Missing CNI default network"
Mar 06 08:58:37 minikube crio[2776]: time="2019-03-06 08:58:37.994773927Z" level=info msg="Initial CNI setting failed, continue monitoring: Missing CNI default network"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.000438209Z" level=debug msg="seccomp status: true"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.001228120Z" level=debug msg="Golang's threads limit set to 12960"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.001917783Z" level=debug msg="sandboxes: []"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.002114770Z" level=debug msg="monitoring "/usr/share/containers/oci/hooks.d" for hooks"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.002168510Z" level=debug msg="monitoring "/etc/containers/oci/hooks.d" for hooks"
Mar 06 08:58:38 minikube systemd[1]: Started Open Container Initiative Daemon.
-- Subject: Unit crio.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit crio.service has finished starting up.
-- 
-- The start-up result is RESULT.
Mar 06 08:58:38 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57971 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:38 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57972 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:38 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57973 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:38 minikube sudo[2812]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/systemctl stop crio
Mar 06 08:58:38 minikube systemd[1]: Stopping Open Container Initiative Daemon...
-- Subject: Unit crio.service has begun shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit crio.service has begun shutting down.
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.335951464Z" level=debug msg="received signal" signal=terminated
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.336336688Z" level=debug msg="Caught SIGTERM"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.336852945Z" level=debug msg="hook monitoring canceled: context canceled"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.336895884Z" level=debug msg="closing exit monitor..."
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.345731812Z" level=debug msg="closed stream server"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.345766727Z" level=debug msg="closed monitors"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.345773470Z" level=debug msg="closed hook monitor"
Mar 06 08:58:38 minikube crio[2776]: time="2019-03-06 08:58:38.345777106Z" level=debug msg="closed main server"
Mar 06 08:58:38 minikube systemd[1]: Stopped Open Container Initiative Daemon.
-- Subject: Unit crio.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit crio.service has finished shutting down.
Mar 06 08:58:38 minikube sudo[2817]:   docker : TTY=unknown ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/systemctl restart docker
Mar 06 08:58:38 minikube systemd[1]: Closed Docker Socket for the API.
-- Subject: Unit docker.socket has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.socket has finished shutting down.
Mar 06 08:58:38 minikube systemd[1]: Stopping Docker Socket for the API.
-- Subject: Unit docker.socket has begun shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.socket has begun shutting down.
Mar 06 08:58:38 minikube systemd[1]: Starting Docker Socket for the API.
-- Subject: Unit docker.socket has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.socket has begun starting up.
Mar 06 08:58:38 minikube systemd[1]: Listening on Docker Socket for the API.
-- Subject: Unit docker.socket has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.socket has finished starting up.
-- 
-- The start-up result is RESULT.
Mar 06 08:58:38 minikube systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.service has begun starting up.
Mar 06 08:58:38 minikube dockerd[2820]: insecure registry eu.gcr.io/goeuro-dev is not valid: invalid host "eu.gcr.io/goeuro-dev"
Mar 06 08:58:38 minikube systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Mar 06 08:58:38 minikube systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 06 08:58:38 minikube systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.service has failed.
-- 
-- The result is RESULT.
Mar 06 08:58:42 minikube kernel: hpet1: lost 320 rtc interrupts
Mar 06 08:58:43 minikube sshd[2136]: Accepted publickey for docker from 10.0.2.2 port 57976 ssh2: RSA SHA256:n+jift3nbiMNxseOU5JtY9TD0Wpnh7GoEskn3ObDfeY
Mar 06 08:58:46 minikube kernel: 00:11:20.238819 timesync vgsvcTimeSyncWorker: Radical guest time change: 32 600 685 416 000ns (GuestNow=1 551 862 726 959 220 000 ns GuestLast=1 551 830 126 273 804 000 ns fSetTimeLastLoop=true )
Mar 06 08:58:46 minikube VBoxService[2045]: 00:11:20.238819 timesync vgsvcTimeSyncWorker: Radical guest time change: 32 600 685 416 000ns (GuestNow=1 551 862 726 959 220 000 ns GuestLast=1 551 830 126 273 804 000 ns fSetTimeLastLoop=true )

I know it's a bit verbose, but I have no idea which parts are the relevant ones.

@afbjorklund
Copy link
Collaborator

This looks odd: insecure registry eu.gcr.io/goeuro-dev is not valid: invalid host "eu.gcr.io/goeuro-dev"

@tstromberg tstromberg changed the title minikube tries to use systemctl to restart docker on macos Failed to enable container runtime: docker restart failed (insecure registry ... invalid host) Mar 8, 2019
@tstromberg tstromberg added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Mar 8, 2019
@tstromberg
Copy link
Contributor

Yeah, I'm deeply suspect about that particular error. Docker inside the VM appears to be misconfigured. Where did that hostname come from?

NOTE: You may setup a new VM by using minikube delete.

@tstromberg tstromberg added the triage/needs-information Indicates an issue needs more information in order to work on it. label Mar 8, 2019
@afbjorklund
Copy link
Collaborator

Something seems gone wrong with the delete (said it had been done before each attempt)

@Freddixx
Copy link
Author

Yes, that must've been it. That hostname definitely came from my side (I was experimenting with insecure registries). I have no idea how that got stuck in there. I ended up deleting everything and it works now.

Thanks for the quick help, after all the attempts I made I think I got blind for that error (which objectively was pretty obvious).

I will close this issue. Thanks again!

@arunsingh
Copy link

same error occurred to me.

@jeenx
Copy link

jeenx commented Apr 25, 2019 •
edited
Loading

@arunsingh I had the same error, but mine was due to running an older version of minikube and not killing the old VM that was running. Running minikube delete and recreating via minikube start did it for me.

@arunsingh
Copy link

Finally I did that only, Running minikube delete and I did not recreated via minikube start , I started all over again, Is there any command to restore backup of pods from same state before doing minikube delete

@win5do win5do mentioned this issue Jun 21, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/docker-env docker-env issues co/virtualbox priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@tstromberg @arunsingh @Freddixx @afbjorklund @jeenx