fix(deploy): drop MicrosoftModule from container + log failed revisions - #85
Merged
Conversation
Keep the ASP.NET 11 RC1 base image, drop the newly added MicrosoftModule from the published module list (it was not in prior working releases), and print Container App console logs when a revision fails.
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
1 participant
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.
Summary
aspnet:11.0.0-rc.1base image.DigitalBrain__Moduleslist to the prior working set (no MicrosoftModule).az containerapp logsfor diagnosis.Why
v0.1.22failed on missing RC1 framework.v0.1.23still Failed after the base-image fix; local repro shows Microsoft module HTTP surface activation can blow up silo startup when membership/clustering wiring is incomplete. Revert modules to the last known-good set and capture Azure logs if it fails again.