Containers fail when hosted in Azure services #4422
Merged
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
DavidBoike
approved these changes
Sep 3, 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
ServiceControl containers do not work in Azure Container Apps or Azure Web Apps due to an exception similar to the following:
This can occur at many levels of the stack, including setup mode for Azure Service Bus when creating queues, or during normal startup as part of assembly scanning.
Who's affected
Users using ServiceControl containers with versions 5.6.0 through 5.7.1.
Root cause
The
noble(Ubuntu 24.04) base image appears to have some OpenSSL compatibility problems when using the containers on Azure, so this PR switches to thejammy(Ubuntu 22.04) base image instead.