docs/quickstart: kind image load fails on Apple M1 about admiralty HOT 4 CLOSED

This seems to be the issue kubernetes-sigs/kind#2549 but I am not sure what the resolution is.

from admiralty.

Hi @ahmetb, I see that you submitted another issue after this one, #149, where you have gone farther in the quick start guide. Were you able to figure out what the problem is here?

Unfortunately, I don't have an M1 available. We do build multi-arch images that are known to work, though aren't systematically tested... Which version of kind are you running? The latest version seems to address some multi-arch issues (not necessarily related):

NOTE: these node images support amd64 and arm64 now.
[...]
Fix kind load docker-image if all images are already present
https://github.com/kubernetes-sigs/kind/releases/tag/v0.12.0

from admiralty.

I'm seeing the same problem.

• If I just run a regular nginx image from docker hub it works.
• If I use the local registry route (using --platform=linux/arm64 images), it also works.

But kind load docker-image:

GOOS=linux GOARCH=arm64 go build -o bin/server example/server
docker build --platform=linux/arm64 -t demo-server-arm64 -f Dockerfile
kind --name=demo load docker-image demo-server-arm64
kubectl create deployment demo-server-arm64 --image demo-server-arm64 --replicas=1
# fails with:
# Failed to pull image "demo-server-arm64": rpc error: code = Unknown desc = failed to pull and unpack
# image "docker.io/library/demo-server-arm64:latest": failed to resolve reference 
# "docker.io/library/demo-server-arm64:latest": pull access denied, repository does not exist 
# or may require authorization: server message: insufficient_scope: authorization failed

GOOS=linux GOARCH=amd64 go build -o bin/server example/server
docker build --platform=linux/amd64 -t demo-server-amd64 -f Dockerfile
kind --name=demo load docker-image demo-server-amd64
# fails with:
# ERROR: failed to load image: command "docker exec --privileged -i demo-control-plane ctr --namespace=k8s.io images import --snapshotter overlayfs -" failed with error: exit status 1
# Command Output: ctr: image might be filtered out

(N.B. Dockerfile is just 1 binary COPY based on scratch)

I have the feeling that somewhere down the line, Kubernetes might be trying to load amd64 images... The fact that NGINX works, can this be because it is a multi-architecture image?

from admiralty.

Tested the v0.16 quickstart with an M1. It works. Probably an issue that was fixed with a recent version kind.

from admiralty.