'mediaType': 'application/.list.

That looks like a manifest, not like a manifest list (a.k.a. Simply starting the dev container using a constant build image: Docker Desktop for Mac v 3.4.0 - docker ps in container works Docker Desktop for Mac v 3.5.x - docker ps in the container fails (points to endpoint other than /var/run/docker.

Here's the right docker info (I hope): $ minikube ssh docker infoĪpp: Docker App (Docker Inc., v0.9.1-beta3)īuildx: Build with BuildKit (Docker Inc., v0.6.1-docker)Ĭontainerd version: e25210fe30a0a703442421b0f60afac609f950a3 For some reason the auth is failing against AWS ECR 🙈

I'm working on pulling an image from the node. Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Network: bridge host ipvlan macvlan null overlay I first discussed this here: Operating System When I run the image using docker run it runs as an aarch64, however when I launch a pod on K8s with exactly the same image, it’ll run the x86 variant. I have a docker image that is available for both x86 and aarch64. It's probably not a Docker for Mac issue, because it resolves to the right architecture. I’m running minikube with the docker driver on Docker for Mac on Apple Silicon. I don't know which component involved (minikube, k8s or Docker for Mac) is causing the problem. Manually specifying the or using an arm64 image tagged with -arm64 solves the problem. It seems that the node is marked correctly as arm64. Minikube Ready control-plane,master 33d v1.22.3 /arch=arm64,/os=linux,kubernetes.io/arch=arm64.

When I run the image using “docker run” it runs as an aarch64, however when I launch a pod on K8s with exactly the same image, it’ll run the x86 variant. I’m running minikube with the docker driver on Docker for Mac on Apple Silicon. Minikube is not running arm64 images even though they are available when running on Docker for Mac (Apple Silicon)

Running docker image docker for mac