Failed to start on Raspberry Pi OS arm(v7)

[kristianpaul]

Steps to reproduce the issue:

1. curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-arm
2. sudo install minikube-linux-arm /usr/local/bin/minikube
3. minikube start

minikube  start
😄  minikube v1.22.0 on Raspbian 10.10 (arm)
✨  Using the docker driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
E0729 03:55:06.239878    2022 cache.go:200] Error downloading kic artifacts:  failed to download kic base image or any fallback image
🤷  docker "minikube" container is missing, will recreate.
🔥  Creating docker container (CPUs=2, Memory=2200MB) ...
🤦  StartHost failed, but will try again: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.25@sha256:6f936e3443b95cd918d77623bf7b595653bb382766e280290a02b4a349e88b79 -d /var/lib: exit status 125
stdout:

stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.25@sha256:6f936e3443b95cd918d77623bf7b595653bb382766e280290a02b4a349e88b79' locally
sha256:6f936e3443b95cd918d77623bf7b595653bb382766e280290a02b4a349e88b79: Pulling from k8s-minikube/kicbase
docker: no matching manifest for unknown in the manifest list entries.
See 'docker run --help'.

pi@rpi1:~ $ minikube start 😄 minikube v1.22.0 on Raspbian 10.10 (arm) ✨ Using the docker driver based on existing profile 👍 Starting control plane node minikube in cluster minikube 🚜 Pulling base image ... E0729 03:57:22.918515 2692 cache.go:200] Error downloading kic artifacts: failed to download kic base image or any fallback image 🤷 docker "minikube" container is missing, will recreate. 🔥 Creating docker container (CPUs=2, Memory=2200MB) ... 🤦 StartHost failed, but will try again: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.25@sha256:6f936e3443b95cd918d77623bf7b595653bb382766e280290a02b4a349e88b79 -d /var/lib: exit status 125 stdout:

stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.25@sha256:6f936e3443b95cd918d77623bf7b595653bb382766e280290a02b4a349e88b79' locally
sha256:6f936e3443b95cd918d77623bf7b595653bb382766e280290a02b4a349e88b79: Pulling from k8s-minikube/kicbase
docker: no matching manifest for unknown in the manifest list entries.
See 'docker run --help'.

lastStart.txt

[medyagh]

I am curious can you pull the image manually?

docker pull gcr.io/k8s-minikube/kicbase:v0.0.25

[afbjorklund]

There is currently no support for arm(32), only arm64.

The error is: failed to download gcr.io/k8s-minikube/kicbase:v0.0.25@sha256:6f936e3443b95cd918d77623bf7b595653bb382766e280290a02b4a349e88b79, will try fallback image if available: getting remote image: no child with platform linux/arm in index gcr.io/k8s-minikube/kicbase:v0.0.25@sha256:6f936e3443b95cd918d77623bf7b595653bb382766e280290a02b4a349e88b79

Eventually need to build kicbase for both architectures...

docker info

OperatingSystem:Raspbian GNU/Linux 10 (buster)
OSType:linux
Architecture:armv7l

KICBASE_ARCH = linux/arm64,linux/amd64

[afbjorklund]

There is a beta version available, of Raspberry Pi OS 64-bit
https://downloads.raspberrypi.org/raspios_arm64/images/

https://www.raspberrypi.org/blog/latest-raspberry-pi-os-update-may-2020/
(there are some more Raspberry Pi details under the backlog item #9762)

[afbjorklund]

I made a PR to include "arm" in the kicbase arch: #12079

[sharifelgamal]

This isn't quite ready yet (that previous PR didn't build on armv7) but we have a tracking issue for the docker driver on armv7 specifically: #12399

[k8s-triage-robot]

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:

• 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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:

• 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[spowelljr]

arm should now be available since a couple releases ago, you can view all our release artifacts here https://github.com/kubernetes/minikube/releases/tag/v1.25.2

I'm going to close this issue, but if you have any further questions feel free to reopen and respond, thanks!