minikube v1.18.1 not finishing on Fedora 33 using Podman and-or CRI-O #10737
Comments
|
If you are using the "podman" driver, you don't have to install software (cri-o, conntrack) also on the host. I think the actual issue is the same as #10649 - it got broken in the podman3 upgrade, worked in podman2 |
afbjorklund
added
co/podman-driver
|
I've updated the issue with my Podman version, you are correct. I'm on Podman v3. I thought I was still on Podman v2. ➜ ~ podman version
Version: 3.0.1
API Version: 3.0.0
Go Version: go1.15.8
Built: Fri Feb 19 10:56:17 2021
OS/Arch: linux/amd64 |
|
Using the --container-runtime=docker also seems to work, so it's something with the combo podman3 + cri-o |
|
My run of Docker-CE: #10754 No luck on my side. |
|
Thanks for testing, it worked on Ubuntu 20.04 (with podman version 3.0.1) But I think you misunderstood, I meant --driver=podman --container-runtime=docker |
|
The safe bet is otherwise to use a VM (--vm=true), see #10237 (comment) There are a lot of experimental things happening at once in Fedora, otherwise |
|
That's what I feared. I didn't want to run more VM's on my system already, but I'm thinking Ubuntu may be what I try next to get this all working. |
|
It is supposed to work, to use the "alternative" Fedora and Podman and CRI-O too... Just that it is less tested, and less stable, than using Ubuntu and Docker and Docker. We could need some community support for local Kubernetes, especially testing ? Red Hat is mostly focusing on OpenShift and CodeReady Containers (minishift4) |
|
I'd be willing to help test, just need to know what would need to be done to test and what we're looking for. Since I haven't had a plain Kubernetes install yet work on Fedora with CRI-O, or much luck getting all of that to work except k3s using containerd-shims. |
|
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. |
k8s-ci-robot
added
the
lifecycle/stale
|
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. |
k8s-ci-robot
added
lifecycle/rotten
ilya-zuyev
removed
the
lifecycle/rotten
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
sharifelgamal
removed
the
lifecycle/stale
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
k8s-ci-robot
added
lifecycle/rotten
Description
Steps to reproduce the issue:
sudo dnf module list cri-osudo dnf module enable cri-o:1.20sudo dnf install cri-osudo dnf install conntrackminikube config set driver podmansudo visudo --file=/etc/sudoers.d/podmanminikube start --driver=podman --container-runtime=cri-o --extra-config=kubelet.cgroup-driver=systemd --alsologtostderr -v=7 2>&1 | tee minikube_2021-03-06_Fedroa-33_podman_on_cri-o.logsudo journalctl -xeu kubelet --no-pagerminikube stopminikube deleteFull output of failed command:
Log output hidden. Expand details for full logs.
Full output of
minikube startcommand used, if not already included:See above.
Minikube Logs
Optional: Full output of
minikube logscommand:The text was updated successfully, but these errors were encountered: