Restoring db crash

Docker Desktop
,
1

I have a docker container with this setting

docker run -d --name sql2025 --cpuset-cpus="0" -p 1433:1433 -e ACCEPT_EULA=Y -e SA_PASSWORDxxxx -e MSSQL_PID=developer -v C:\DockerDB:/var/opt/mssql/data mcr.microsoft.com/mssql/server:2025-latest

I tried different configuration for cpuset :
without the setting or 0-5 , 0-3, 0-2,0-1 and the last 0

when I try to restore some db the server crash with the follow error

This program has encountered a fatal error and cannot continue running at Wed Mar 18 11:28:10 2026
The following diagnostic information is available:

         Reason: 0x00000004
        Message: ASSERT: Expression=((seenByMonitor) <(NonYieldThreshold)) File=LibOS\Windows\Kernel\SQLPal\common\dk\sos\src\sosschedmon.cpp Line=202
    Stack Trace:
                 file://package6/windows/system32/sqlpal.dll+0x000000000000A5D6
                 file://package6/windows/system32/sqlpal.dll+0x0000000000009909
                 file://package6/windows/system32/sqlpal.dll+0x00000000000055D4
                 file://package6/windows/system32/sqlpal.dll+0x00000000000F1055
                 file://package6/windows/system32/sqlpal.dll+0x00000000000F0ADF
                 file://package6/windows/system32/sqlpal.dll+0x00000000000E351A
                 file://package6/windows/system32/sqlpal.dll+0x00000000000A8BF1
                 file://package6/windows/system32/sqlpal.dll+0x00000000000A8E51
                 file://package6/windows/system32/sqlpal.dll+0x000000000000510C
        Process: 12 - sqlservr
         Thread: 19 (application thread 0x14)
    Instance Id: 4351f7cb-c44b-49e3-ac2d-0461df960cbf
       Crash Id: 1756913f-c7a6-4256-8976-a3d828f87a44
    Build stamp: 1dc5d1603aa64f486a93228f7623fc344f4374e76f090c5e8a58b346f39f7350
   Distribution: Ubuntu 24.04.4 LTS
     Processors: 1
   Total Memory: 16421961728 bytes
      Timestamp: Wed Mar 18 11:28:10 2026

if I restore the backup in a windows version I havn’t no problem.
what can I do to resolve the problem?

2

I made also a new test, if I try the same backup in a 2022 docker container it works, so the problem is with the 2025

3

Thank you for keeping us in the loop!