Closed criztovyl closed 2 years ago
Isn't this a bug, not support?
while trying to reproduce today my podman container started successfully (the podman bug i am sometimes running into did not occur), but I submitted the PR above that should fix what I discovered.
I'll report back when I can verify it with a container that fails to start.
minikube start --nodes=4 ๐ minikube v1.33.1 on Darwin 14.3 (arm64) โช MINIKUBE_ROOTLESS=true โจ Using the podman (experimental) driver based on existing profile โ You cannot change the number of nodes for an existing minikube cluster. Please use 'minikube node add' to add nodes to an existing cluster. ๐ Starting "minikube" primary control-plane node in "minikube" cluster ๐ Pulling base image v0.0.44 ... E0830 13:46:25.454194 3401 cache.go:189] Error downloading kic artifacts: not yet implemented, see issue #8426 ๐ Restarting existing podman container for "minikube" ... ๐คฆ StartHost failed, but will try again: driver start: start: podman start minikube: exit status 125 stdout:
stderr: Error: no container with name or ID "minikube" found: no such container
๐ Restarting existing podman container for "minikube" ... ๐ฟ Failed to start podman container. Running "minikube delete" may fix it: driver start: start: podman start minikube: exit status 125 stdout:
stderr: Error: no container with name or ID "minikube" found: no such container
โ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: driver start: start: podman start minikube: exit status 125 stdout:
stderr: Error: no container with name or ID "minikube" found: no such container
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ โ
โ ๐ฟ If the above advice does not help, please let us know: โ
โ ๐ https://github.com/kubernetes/minikube/issues/new/choose โ
โ โ
โ Please run minikube logs --file=logs.txt
and attach logs.txt to the GitHub issue. โ
โ โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
I am getting this, can anyone help me to sort this out
MacOS Podman
looks unrelated to this issue, if this still occurs, please open a new one.
What Happened?
When podman fails to start minikubes container, minikube seems to ignore that error and runs into an exponential-backoff retring to ssh into the (failed to start) container.
From reading the source I think the bug is in
kic
Driver.Start()
https://github.com/kubernetes/minikube/blob/b496d669e79fc0d34fe1309d8c0dfde9c8271f6d/pkg/drivers/kic/kic.go#L399-L407
StartContainer()
will properly return the error, andStart()
goes intoerr != nil
block as visible in the log (Postmortem inspect
). NormallyStart()
wouldreturn errors.Wrap(err, "start")
, but:err
ofStartContainer()
is overwritten witherr
fromoci.DeamonInfo()
DaemonInfo()
err
isnil
Wrap()
returnsnil
iferr
isnil
StartContainer()
also returnsnil
.Attach the log file
Operating System
Other (Debian)
Driver
Podman