fix: Update mssql.Dockerfile server:2022-latest to newer pin#267
Merged
darcywong00 merged 3 commits intostagingfrom Jan 30, 2025
Merged
fix: Update mssql.Dockerfile server:2022-latest to newer pin#267darcywong00 merged 3 commits intostagingfrom
darcywong00 merged 3 commits intostagingfrom
Conversation
Reverts #217 Attempting to get a fixed server:2022 image that will run on the new CI cluster (newer kernel).
Member
|
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
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.
Follows #217. Fixes #268
Attempting to get a fixed server:2022 image that will run on the new CI cluster (newer kernel).
So @tim-eves can progress on the staging site migration.
Locally, I run into an SQL exception in /tools/db/build/build.inc.php:153
I suspect the region "001" is getting truncated to "00". But will have to chase separately...
(update)
This was fixed by #246 in master branch, so updating staging fixes the error.