Open slinkydeveloper opened 4 years ago
Thank you for sharing your experience! If you don't mind, could you please provide:
@slinkydeveloper do you happen to be using VPN or a firewall that limits your network connectivit ? and what version of qemu or libvirt are you using ? (sometimes upgrading the kvm libs fixes kvm issues)
and additionally I am curious is there a reason you are not using the docker driver which is our most preferred driver?
/triage needs-information /triage support
do you happen to be using VPN or a firewall that limits your network connectivit ?
Nope, I just have the default network configuration of fedora 32 and no vpn running
Name : libvirt Version : 6.1.0 Rilascio : 4.fc32 Architecture : x86_64 Size : 0.0
Sorgente : libvirt-6.1.0-4.fc32.src.rpmName : qemu Epoca : 2 Version : 4.2.1 Rilascio : 1.fc32 Architecture : x86_64 Size : 12 k Sorgente : qemu-4.2.1-1.fc32.src.rpm
@slinkydeveloper does switching to docker driver help you solve this problem ?
you could try with latest verison of miniikube minikube delete minikube start --driver=docker
for more information on the docker driver checkout: https://minikube.sigs.k8s.io/docs/drivers/docker/
/triage needs-information /triage support
I'm trying to install it, but for some reason i get Can not load RPM file: ./minikube-latest.x86-64.rpm.
when using dnf...
@slinkydeveloper do you still have this issue ? btw I recommend using our docker driver on linux
Just an observer here -- I've subscribed to this issue because I had following error on Fedora 32 due to a clash between moby
and libvirt
:
COMMAND_FAILED: 'python-nftables' failed:
JSON blob:
{"nftables": [{"metainfo": {"json_schema_version": 1}}, ...
Since subscribing to this issue, I've resolved it as suggested on the Red Hat Bugzilla and, i.e. by removing the incorrect /etc/firewalld/zones/trusted.xml
file:
sudo mv /etc/firewalld/zones/trusted.xml /etc/firewalld/zones/trusted.xml.bkp
sudo systemctl restart firewalld
sudo systemctl restart libvirtd
Thanks @szarnyasg, it's the same issue as described here https://github.com/code-ready/crc/issues/1444
@szarnyasg - thanks for the workaround!
There is probably nothing we can do about this - so I'm going to leave this.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
anyone like to add this as a work arround to either minikube Solution messages or our website I would accept a PR btw @slinkydeveloper seems like our website for RPM URL was missing -
could u try with https://storage.googleapis.com/minikube/releases/latest/minikube-latest.x86_64.rpm
Steps to reproduce the issue:
minikube start --vm-driver=kvm2
without any previous minikube data (no~/.minikube
dir)Fedora 32, kernel 5.7.8-200.fc32.x86_64
Full output of failed command: