mssql-docker icon indicating copy to clipboard operation
mssql-docker copied to clipboard

Current 2022-latest image fails on macOS ARM under Rosetta

Open mcx808 opened this issue 8 months ago • 2 comments

While troubleshooting the SQL 2022 container setup on a second mac, I noticed the issue was with the specific image mcr.microsoft.com/mssql/server@sha256:2b41d0be82839692f678a709e8b7dd6106ee4776b0e70759c59b067730058b04

The container constantly restart without actually providing any error.

I reverted to the previous version on my main machine sha256:b283d9eef2544af92aeb38f8bb3d55ce17de037eafb04eeeb3ee2c52033476ec which worked again, and also worked when I deployed to 2 additional Macs.

All systems are running macOS 15.3 on M2 CPUs and using Apple Virtualization Framework with Rosetta for x86, although I had the same problem with SQL when switching to either QEMU or Docker VMM. I think all machines had various versions of Docker but all were updated to v4.39.0 to rule out any issues there.

Seems strange that a minor version update to MSSQL would cause architecture-level issues, unless something changed in the container build between these versions. Since the mcr.microsoft.com is light on metadata I can't really inspect the changes between versions very well.

mcx808 avatar Apr 01 '25 08:04 mcx808

Did you try restarting your Mac(s)?

I'm not being sarcastic, but a colleague next to me just restarted her laptop after running into a problem where the container wouldn't start. My system and her Docker Desktop were configured to use Apple Virtualization framework with "Use Rosetta for x86+64/amd64 emulation on Apple Silicon" and mine was working but hers wasn't. She just restarted her Mac and it started working.

Not really a good solution, but still worth ruling out.

zerodivide1 avatar Jul 09 '25 21:07 zerodivide1

Yes, since this issue has been present over a long time with multiple machines.

I've also switched to Orbstack in the meantime as my docker engine but the issue is still present in 2022-latest

I'm just sticking with the working version until this is fixed.

mcx808 avatar Jul 14 '25 15:07 mcx808