[8.x](backport #41104) x-pack/metricbeat/module/mssql: Update mssql image version to avoid SIGABRT and update HEALTHCHECK #41113
+4
−4
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.
Proposed commit message
Related: microsoft/mssql-docker#868, microsoft/mssql-docker#881, sqldef/sqldef#560 (comment) (etc.)
Reported first here: #40924 (comment)
For 6.7 Linux Kernel, the 2017, 2019, and 2022 mssql versions started breaking. Microsoft has updated some images and now they are working. Please take a look at the linked issues for more info.
Not adding a CHANGELOG entry as it's a change that only impacts integration tests.
There's one more change that is required to fix another issue: elastic/integrations#10899; I fixed the same issue in integrations a couple of months back. Done the same here.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.This is an automatic backport of pull request #41104 done by [Mergify](https://mergify.com).