ServiceControl containers fail when using SQL Transport #4437
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
bording
approved these changes
Sep 10, 2024
DavidBoike
changed the title
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.
Symptoms
Container-hosted ServiceControl instances attempting to use SQL Transport will faill with the following exception:
Who's affected
Users running ServiceControl on Linux containers attempting to configure the containers to use SQL Transport.
Root cause
ServiceControl uses a "chiseled" base image to provide a smaller image size and reduced attack surface, as chiseled images do not contain things like a shell or
apt-getnot needed to run the application. However, thejammy-chiseled-compositebase container does not contain globalization libraries which are required by the SQL Client to support things like database collation settings.