Fix: align Dockerfile PORT with Container App targetPort#4
Merged
Conversation
The Container App ingress routes to port 3000, but commit f369086 changed the Dockerfile to PORT=8347. This caused the new revision to be unreachable (Unhealthy/Degraded), with Container Apps falling back to the old April 1 revision that lacks the /api/catalog route. Reverting to PORT=3000 restores connectivity so the latest revision serves all routes including the catalog endpoint.
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
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.
Root Cause
Commit f369086 changed the Dockerfile from
PORT=3000toPORT=8347to follow the port assignment policy, but the Azure Container App's ingresstargetPortwas never updated from 3000.This caused:
/api/catalog(added later) → 404 errors/api/health→ appears to work fineFix
Revert
ENV PORTandEXPOSEto 3000 in the Dockerfile to match the Container App'stargetPort: 3000. Once the new revision starts on port 3000, the ingress proxy can reach it, and all routes (including/api/catalog) will be served from the latest code.Alert Reference
Triggered by production alert at 2026-04-20T16:40:04.580Z: 13 errors on
ideaplaces-websitefetchinghttps://c3.ideaplaces.com/api/catalog(404).Testing
/api/health(200) and/api/catalog(200) respond correctly