minikube start fails on ppc64le ubuntu 22.04

Sapana-Khemkar commented 4 months ago

What Happened?

root@dotnet-ubuntu-2204-2:~# minikube start --driver=docker --force

minikube v1.33.0 on Ubuntu 22.04 (ppc64le) ! minikube skips various validations when --force is supplied; this may lead to unexpected behavior
Using the docker driver based on user configuration
The "docker" driver should not be used with root privileges. If you wish to continue as root, use --force.
If you are running minikube within a VM, consider using --driver=none:
https://minikube.sigs.k8s.io/docs/reference/drivers/none/
Using Docker driver with root privileges
Starting "minikube" primary control-plane node in "minikube" cluster
Pulling base image v0.0.43 ...
Creating docker container (CPUs=2, Memory=4000MB) ...

X Exiting due to RUNTIME_ENABLE: Failed to start container runtime: which crictl: Process exited with status 1 stdout:

stderr:

╭─────────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ 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. │ │ │ ╰─────────────────────────────────────────────────────────────────────────────────────────────╯

Attach the log file

log.txt

Operating System

Ubuntu

Driver

Docker

Sapana-Khemkar commented 4 months ago

I updated kicbase dockerfile with below patch and built image on power vm. Used locally build base image using command minikube start --driver=docker --base-image=local/kicbase:latest --force then above issue get fixed.

[root@apic-team-vm1 minikube]# git diff
diff --git a/deploy/kicbase/Dockerfile b/deploy/kicbase/Dockerfile
index eb505a362..6877d0408 100644
--- a/deploy/kicbase/Dockerfile
+++ b/deploy/kicbase/Dockerfile
 @@ -195,7 +195,11 @@ RUN export ARCH=$(dpkg --print-architecture | sed 's/ppc64el/ppc64le/') && \
     if [ "$ARCH" != "ppc64le" ]; then \
         clean-install catatonit conmon cri-tools crun; \
     else \
-        clean-install conmon crun; \
+        clean-install conmon crun && \
+        export CRICTL_VERSION="v1.30.0" && \
+        curl -LO https://github.com/kubernetes-sigs/cri-tools/releases/download/$CRICTL_VERSION/crictl-$CRICTL_VERSION-linux-ppc64le.tar.gz && \
+        tar zxvf crictl-$CRICTL_VERSION-linux-ppc64le.tar.gz -C /usr/bin &&\
+        rm -f crictl-$CRICTL_VERSION-linux-ppc64le.tar.gz; \
     fi

iv1111 commented 4 months ago

Hi, @mkumatag. Any way you could review this one? Thanks!

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 week ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

kubernetes / minikube