Fixes #9251. Use SQL Server 2022 image on FIPS - #9253
Open
JiriOndrusek wants to merge 1 commit into
Open
JiriOndrusek wants to merge 1 commit into
JiriOndrusek wants to merge 1 commit into
Conversation
The SQL Server 2025 container image crashes on FIPS enabled hosts during TLS initialization (errors 49946/49947, exit code 151), see microsoft/mssql-docker#958. The container never starts, so CamelMssqlJdbcTest and other MS SQL based tests fail. - root pom: `fips` profile overrides sql-server.container.image with mcr.microsoft.com/mssql/server:2022-latest (the last image that starts on FIPS) - jdbc/mssql: honour sql-server.container.image via the dev service image-name, like the mysql/oracle/postgresql modules already do (it was falling back to the Quarkus default before) - debezium-grouped README: fix the stale MS SQL EULA image tag (2022-latest -> 2025-latest) to match the current default image Regular (non-FIPS) runs keep using 2025-latest. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
aldettinger
approved these changes
Sep 29, 2026
Contributor
|
I am curious whether the RHEL variant of the SQL Server image might work out of the box with FIPS? https://mcr.microsoft.com/en-us/artifact/mar/mssql/rhel/server/tag/2025-latest If it's a pain to test, then don't bother. But it might simplify things compared to needing 2 different image versions. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #9251
The SQL Server 2025 container image crashes on FIPS enabled hosts during TLS initialization (errors 49946/49947, exit code 151), see microsoft/mssql-docker#958. The container never starts, so
CamelMssqlJdbcTestand other MS SQL based tests fail.fipsprofile overridessql-server.container.imagewithmcr.microsoft.com/mssql/server:2022-latest(the last image that starts on FIPS)sql-server.container.imagevia the dev serviceimage-name, like the mysql/oracle/postgresql modules already do (it was falling back to the Quarkus default before)Regular (non-FIPS) runs keep using 2025-latest. The
fipsoverride also covers jdbc-grouped and the Debezium MS SQL test, which read the same property.🤖 Generated with Claude Code