-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
Fedora 32, kvm: COMMAND_FAILED: 'python-nftables' failed #8772
Comments
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 additionally I am curious is there a reason you are not using the docker driver which is our most preferred driver? /triage needs-information |
Nope, I just have the default network configuration of fedora 32 and no vpn running
|
@slinkydeveloper does switching to docker driver help you solve this problem ? you could try with latest verison of miniikube for more information on the docker driver checkout: /triage needs-information |
I'm trying to install it, but for some reason i get |
@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 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 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 crc-org/crc#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. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
anyone like to add this as a work arround to either minikube Solution messages or our website I would accept a PR 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:
The text was updated successfully, but these errors were encountered: