I've been using Docker Compose on my Mac mini for years without issues, running around 11 images in my composer file. But today, after restarting my Mac, I've encountered a frustrating error: "no matching manifest for linux/arm64/v8 in the manifest list entries." The images come from various sources, so I don't think it's an image problem. I ran 'docker buildx imagetools inspect' on them and each one lists linux/arm as an available image. My Docker Desktop is updated to the latest version, and I even cleared all cache files. No changes were made to the composer .yml file either.
I also attempted to add 'platform: linux/arm64' to all my services, but that didn't solve the issue. However, when I execute a manual command like 'docker run --platform linux/arm64 lscr.io/linuxserver/overseerr:latest', it works just fine. So, why isn't the composer yml working? What can I do to get my Docker stack back up and running?
2 Answers
If you're still stuck, consider trying alternatives like Orbstack or Colima. These tools can sometimes offer better compatibility with M1 Macs. They might help you bypass the current issue entirely, though you'd want to do a bit of research on their pros and cons first.
It seems like you might have run into a docker desktop update that altered the container runtime or some settings. If it worked before, something must have changed. I suggest checking your Docker settings and logs for any clues about what might have happened. Just to clarify, have you tried running Docker in a different configuration or checking for any compatibility issues?
Yeah, I did check the logs and they didn't indicate any issues, but it’s worth diving deeper into settings. I might also try rolling back to a prior version of Docker Desktop to see if that helps.
I'd like to know more about those tools too. Are they actually better, or just different? I don't want to make things more complicated for myself without a good reason.