fix(ui): listen on 8080 to match the UI image's own port - #17
Merged
Merged
Conversation
The UI image serves on 8080 and its baked-in healthcheck probes http://127.0.0.1:8080/. devkit mounts its own default.conf over the image's server block, and that conf listened on 80 — so nginx bound 80, the SPA served correctly, and the healthcheck got connection refused. The container has sat permanently (unhealthy) for every UI tag published since the image moved to 8080, including the UI_TAG in .env.example. Nothing gates on duplo-ui's health, so serving was never affected. The cost is a status that misreports, and a conf mount that masks the port the image actually uses — so exercising a UI tag in devkit says nothing about how that image behaves where the port matters. - nginx/default.conf: listen 8080 - docker-compose.yml: map ${UI_PORT:-4200} to 8080 localhost:${UI_PORT} is unchanged from the user's side. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
aboutte
force-pushed
the
fix/ui-nginx-port-8080
branch
from
September 28, 2026 18:24
4e000ed to
e12ce21
Compare
aboutte
changed the title
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.
Why
The UI image serves on 8080, and its baked-in healthcheck probes
http://127.0.0.1:8080/. devkit mounts its ownnginx/default.confover the image's server block, and that conf listened on 80.To be precise about the failure mode, since an earlier version of this PR got it wrong: nginx does bind 80 successfully even as UID 65532 — Docker sets
ip_unprivileged_port_start=0, so there are no privileged ports in a container. The SPA serves fine. What breaks is only the healthcheck, which finds nothing on 8080:So
duplo-uihas sat permanently(unhealthy)for every UI tag published since the image moved to 8080 — including theUI_TAGcurrently in.env.example. Nothing in the compose file gates onduplo-ui's health, so serving was never affected. The cost is a status that misreports, plus a conf mount that masks the port the image actually uses.What
nginx/default.conf:listen 80→listen 8080(+ comment)docker-compose.yml:"${UI_PORT:-4200}:80"→"${UI_PORT:-4200}:8080"localhost:${UI_PORT}is unchanged from the user's perspective.Verified
Pre-fix, current
UI_TAG,listen 80: binds 80,curl→ 200, container →(unhealthy), failing streak 3.Post-fix:
Independent of the stuck cluster release — that still needs its own rollback decision.
🤖 Generated with Claude Code