chore: update mssql-2022 to 6249e946 image #299
Closed
Conversation
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
This seemed to fix the error "Could not allocate initial 5000 lock owner blocks during startup." on my machine. I was unable to locate a specific fix relating to the problem, but SQL Server is starting now. Will monitor in case the issue recurs.
User Test ResultsTest specification and instructions User tests are not required |
Member
Author
|
Note: this error recurred on this image, so this didn't fix it. It isn't every run, but it is often enough to be a problem. (Secondary: capturing Docker logs of failed start seems painful) |
Member
Author
|
Holding off update since this did not resolve the issue. |
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.
This seemed to fix the error "Could not allocate initial 5000 lock owner blocks during startup." on my machine. I was unable to locate a specific fix relating to the problem, but SQL Server is starting now. Will monitor in case the issue recurs.
Test-bot: skip