😄 minikube v1.25.2 on Fedora 35
✨ Using the podman driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
E0320 19:00:40.399470 94643 cache.go:203] Error downloading kic artifacts: not yet implemented, see issue #8426
🏃 Updating the running podman "minikube" container ...
❌ Exiting due to RUNTIME_ENABLE: generateCRIOConfig: /bin/bash -c "sudo sed -e 's|^.*pause_image = .*$|pause_image = "k8s.gcr.io/pause:3.6"|' -i /etc/crio/crio.conf.d/02-crio.conf": Process exited with status 2
stdout:
stderr:
sed: can't read /etc/crio/crio.conf.d/02-crio.conf: No such file or directory
I had it running fine in January.
I am aware that some components were updated since (e.g. kernel, minikube itself) but I don't even know what to start with.
What Happened?
Config:
I had it running fine in January. I am aware that some components were updated since (e.g. kernel, minikube itself) but I don't even know what to start with.
Let me know if I can provide more info.
Attach the log file
logs.txt
Operating System
Redhat/Fedora
Driver
Podman