[2025-latest] Container crashes on macOS 26 (Tahoe)
macOS 26 (Tahoe) is stable live, but mssql 2025 docker image does fail to start with following log output:
SQL Server 2025 will run as non-root by default.
This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
assertion failed [x86_avx_state_ptr->xsave_header.xfeatures == kSupportedXFeatureBits]:
(ThreadContextSignals.cpp:414 rt_sigreturn)
The container started with following command:
docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Str0ng!Passw0rd' -p 1433:1433 --platform linux/amd64 mcr.microsoft.com/mssql/server:2025-latest
OS: macOS 26 Docker Desktop version: 4.44.3 with rosetta and Apple virtualization
Workaround: mssql 2022 still works.
I get the same error, which I reported here.
I get the same error, which I reported here.
@osbeorn I know, but the issue had a different symptom, so I thought a separate issue would be more visible.
Did anyone figure out any work arounds?
We're having the exact same issue. Also doesn't help that .NET Aspire 9.5 now defaults to 2025-latest causing all MacOS ARM development to break. Created a linked issue there #11736
Aspire rolled back: https://github.com/dotnet/aspire/issues/11736
But now I would like to use vectors which are 2025-only. So yeah, sad days.
You know what's hilarious. If you install Parallels you can get SQL Server 2025 running on a Windows Arm install.
So let's review the scoreboard.
- 4 trillion dollar company who creates their own Arm64 laptops custom built for their own Arm64 OS ❌
- 800 employee private german company developing for a competitor OS ✅
We're angry because we care. Please do not force our hands to move away from MSSQL.
I’m migrating from a MacBook Pro M2 to a MacBook Pro M3, and I can confirm that the problem only happens on the new machine. • On the M2, running macOS Sequoia 15.6.1, the image mcr.microsoft.com/mssql/server:2025-latest works normally • On the M3, running macOS Tahoe 26.1, the same image fails to start with the exact error reported in this issue
Initially had the same error on M4 Tahoe 26.1 and docker version 27.5.1. Issue seems resolved after I updated docker to 28.x.
Here I'm using Docker Engine: 29.0.1
I get exactly the same error as described in the issue. Using Docker 28.x on M4 Macbook Pro and MacOS 26.1.
Initially had the same error on M4 Tahoe
26.1and docker version27.5.1. Issue seems resolved after I updated docker to28.x.
I am very curious how you have gotten around this when none of us can, are you doing something unique?
Not sure if I'm doing something unique. I just ran the following command locally:
docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=<password>" -p 1433:1433 --name sqlpreview --hostname sqlpreview --platform=linux/amd64 -d mcr.microsoft.com/mssql/server:2025-latest.
Did have to specifically add the platform, because there is no ARM based image of course. Maybe check if rosetta is enabled. Besides that I really have no clue what im doing differently.
Currently running:
- macOS 26.1
- Rosetta 2 (installed)
- OrbStack v2.0.5
- Docker version 28.5.2, build
ecc6942 -
mssql/server:2025-latestwith creation date:25 Oct 2025 at 2:01
The image does seem to work (with the exact command specified by @aadvandenhoogenband ). Omitting the --platform flag simply causes an error that no image for the architecture is available. So it might have been fixed with a newer Docker engine version.
While I'm happy it seems to work now, we're still not sure if this is because of the docker engine, or something else. Can someone who may still have an older version installed (maybe, please?) confirm if Docker@<28.x doesn't work?
Also, this doesn't mean we wouldn't still love to see a compatible arm64 image. Even if only for (as pointed out earlier) the sake of supporting their own platform.
I am using docker 29 on Mac M4, macOS 26.1, and still got the same error mentioned on https://github.com/microsoft/mssql-docker/issues/942#issue-3441374412.
I even tried the command on https://github.com/microsoft/mssql-docker/issues/942#issuecomment-3574158864. but still got the error.
I wanted to add one more data point.
After reading the steps described here: https://www.nocentino.com/posts/2025-11-26-sql-server-2025-docker-desktop-avx-issue/
I installed OrbStack (latest version) on my MacBook Pro M3 running macOS 26.1 and tested the exact same 2025-latest image — and surprisingly, it works there without the AVX/xsave assertion failure.
So in my case:
Docker Desktop (Engine 28.x or 29.x) → crash
OrbStack → works normally
I wanted to add one more data point.
After reading the steps described here: https://www.nocentino.com/posts/2025-11-26-sql-server-2025-docker-desktop-avx-issue/
I installed OrbStack (latest version) on my MacBook Pro M3 running macOS 26.1 and tested the exact same
2025-latestimage — and surprisingly, it works there without the AVX/xsave assertion failure.So in my case:
Docker Desktop (Engine 28.x or 29.x) → crash OrbStack → works normally
For now, I am going with OrbStack as well. I was able to run the sqlserver image now (previously breaking with Docker Desktop and Colima)
Environment:
- macOS Tahoe 26.1
docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
mcr.microsoft.com/mssql/server 2025-latest 55c3fe0f8428 6 weeks ago 1.79GB
docker context ls
NAME DESCRIPTION DOCKER ENDPOINT ERROR
default Current DOCKER_HOST based configuration unix:///var/run/docker.sock
desktop-linux Docker Desktop unix:///Users/<user>/.docker/run/docker.sock
orbstack * OrbStack unix:///Users/<user>/.orbstack/run/docker.sock
docker logs -f sqlserver
SQL Server 2025 will run as non-root by default.
This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
2025-12-08 14:13:44.14 Server Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2025-12-08 14:13:44.17 Server Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2025-12-08 14:13:44.17 Server Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2025-12-08 14:13:44.17 Server Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2025-12-08 14:13:44.17 Server Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2025-12-08 14:13:44.18 Server Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2025-12-08 14:13:44.19 Server Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2025-12-08 14:13:44.19 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.
2025-12-08 14:13:44.20 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.
2025-12-08 14:13:44.20 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.
2025-12-08 14:13:44.21 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.
2025-12-08 14:13:44.23 Server Microsoft SQL Server 2025 (RTM) - 17.0.1000.7 (X64)
Oct 21 2025 12:05:57
Copyright (C) 2025 Microsoft Corporation
Enterprise Developer Edition (64-bit) on Linux (Ubuntu 22.04.5 LTS) <X64>
2025-12-08 14:13:44.23 Server UTC adjustment: 0:00
...
Thanks for the Orbstack recommendation - I have switched and it works great.