-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azure-sql-edge docker images fail on kernel 6.7+ #893
Comments
This article indicates there won't be any further support releases for azure-sql-edge |
Hello, I'm using mcr.microsoft.com/azure-sql-edge:latest on my M1 Mac, is there a better image to run MSSQL in Docker? |
azure-sql-edge does no longer support Apple Silicon, see https://techcommunity.microsoft.com/t5/sql-server-blog/azure-sql-edge-update-september-2023/ba-p/3930827 Good news: Docker for Mac includes virtualization for AMD images (under Settings > General), so it's possible to use the image mcr.microsoft.com/mssql/server:2022-latest which includes the fix for the newer linux kernels. See also https://www.justinjbird.me/blog/2024/running-sql-server-on-macos-using-docker/ |
@nuarhu thank you so much ! :-D |
Also, the latest Cumulative Update for the SQL Server 2019 container includes the fixes, so I was able to get that working on my latest docker install (34) |
Hey there,
this is a follow up to #868 , which was about a bug that prevented the MSSQL server container to start on docker when running on kernel 6.7 and later.
The bug seems to also affect azure-sql-server images, whose last update was 13 months ago (so before the fix for mssql-server was released).
This has been reported by several users whose workflow was broken after updating to Docker Desktop 4.33, which ships kernel 6.10: issue
Additionally, users also report non-2022
mssql-server
images being affected by the issue.Questions:
azure-sql-edge
images to include the fix for kernel 6.7+?mssql-server
images to include the fix?Thanks!
The text was updated successfully, but these errors were encountered: