Summary
The Microsoft SQL Server provider tests (net8.0) job can fail before tests start because the mcr.microsoft.com/mssql/server:latest container exits during startup.
Occurrence
The failure occurs in the Start SQL Server step. The container reports:
Container mssql is unhealthy.
SQL Server 2025 will run as non-root by default.
This program has encountered a fatal error and cannot continue running
Reason: 0x00000002
Last errno: 11
Last errno text: Resource temporarily unavailable
status=exited health=unhealthy restartCount=0 oomKilled=false exitCode=1
SQL Server generated a core dump and exited before any Orleans test executed. PR #10779 only changes grain read-scaling documentation and its compiled sample, so this is unrelated to the PR.
Expected behavior
The SQL Server CI service starts reliably so the provider test job reaches test execution. Consider pinning MSSQL_IMAGE to a validated image digest/version or adding bounded startup recovery for this container failure mode.
Related issues
#10808 and #10900 track database reset races after SQL Server starts; they do not cover this container startup crash. Searches for the fatal reason, unhealthy container message, SQL Server 2025 startup crashes, and open/merged image-pinning PRs found no existing Orleans tracker.
Summary
The
Microsoft SQL Server provider tests (net8.0)job can fail before tests start because themcr.microsoft.com/mssql/server:latestcontainer exits during startup.Occurrence
bbedf80c1eece39ec7b740679afa416aa370de43mcr.microsoft.com/mssql/server:latestThe failure occurs in the
Start SQL Serverstep. The container reports:SQL Server generated a core dump and exited before any Orleans test executed. PR #10779 only changes grain read-scaling documentation and its compiled sample, so this is unrelated to the PR.
Expected behavior
The SQL Server CI service starts reliably so the provider test job reaches test execution. Consider pinning
MSSQL_IMAGEto a validated image digest/version or adding bounded startup recovery for this container failure mode.Related issues
#10808 and #10900 track database reset races after SQL Server starts; they do not cover this container startup crash. Searches for the fatal reason, unhealthy container message, SQL Server 2025 startup crashes, and open/merged image-pinning PRs found no existing Orleans tracker.