[2025-latest] Container crashes on macOS 26 (Tahoe)

[wiruzman]

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.

[osbeorn]

I get the same error, which I reported here.

[wiruzman]

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.

[gregpakes]

Did anyone figure out any work arounds?

[ArnoZeelmaekers]

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

[mattleibow]

Aspire rolled back: dotnet/aspire#11736

But now I would like to use vectors which are 2025-only. So yeah, sad days.

[TaylorWatson]

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.

[wesleyteixeira]

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

[aadvandenhoogenband]

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.

[wesleyteixeira]

Here I'm using Docker Engine: 29.0.1

[jvalkeejarvi]

I get exactly the same error as described in the issue. Using Docker 28.x on M4 Macbook Pro and MacOS 26.1.