You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Microsoft SQL Server Docker image is not compatible with ARM devices, such as Macs with Apple Silicon. Instead, you can use the [SqlEdge](https://www.nuget.org/packages/Testcontainers.SqlEdge) module or [Testcontainers Cloud](https://www.testcontainers.cloud/).
I think it would be smart to point out the SQL Server image can run fine on ARM Mac using Rosetta.
At least in using Docker desktop this works fine:
SQL Edge also has some downsides:
However, using Azure SQL Edge does have some drawbacks. First, you cannot develop against a specific SQL Server 2017/2019/2022 version with Azure SQL Edge. Second, SQL Edge’s unsupported features impose a limit on some scenarios, including: In-Memory OLTP, CLR, and CLR based data types.
Thanks for sharing the issue/enhancement. I totally forgot about the documentation. I replaced Azure SQL Edge with PostgreSQL some time ago (#1156) after Microsoft announced they would no longer continue developing or supporting it.
I suggest changing the documentation to indicate that the referenced example uses PostgreSQL. Then, add the information about Rosetta to the MSSQL module documentation. WDYT?
Problem
The docs say:
testcontainers-dotnet/docs/examples/aspnet.md
Line 84 in a0f1f76
I think it would be smart to point out the SQL Server image can run fine on ARM Mac using Rosetta.
At least in using Docker desktop this works fine:
SQL Edge also has some downsides:
Source: https://techcommunity.microsoft.com/t5/sql-server-blog/azure-sql-edge-update-september-2023/ba-p/3930827
Solution
Improve the example with info on how to run the SQL Server.
Another alternative is to remove those details from the example and move it to
https://dotnet.testcontainers.org/modules/mssql/
Benefit
Improved documentation.
Alternatives
Leave the docs as is.
Would you like to help contributing this enhancement?
Yes
The text was updated successfully, but these errors were encountered: