REG-22126 fix standalone docker port mapping to match :latest image#8
Open
echerry-rs wants to merge 1 commit into
Open
REG-22126 fix standalone docker port mapping to match :latest image#8echerry-rs wants to merge 1 commit into
echerry-rs wants to merge 1 commit into
Conversation
The current regscale/regscale:latest image (rebuilt 2026-05-05) sets ASPNETCORE_URLS=http://+:80 and listens on container port 80, but the standalone compose files mapped host 80 to container 8080, so the UI was unreachable on http://localhost after a fresh install. Aligns both standalone compose files (docker-compose.yml and the azure-sql-edge variant, which uses the same regscale/regscale:latest image) with the image's actual listener port. Verified by Jim Townsend end-to-end: changing this mapping restored UI access against the current :latest image.
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
Fixes REG-22126: after a fresh
standalone_regscale.pyinstall, the UI is unreachable onhttp://localhost. Reported and verified end-to-end by Jim Townsend.Root cause: the public
regscale/regscale:latestimage was rebuilt on 2026-05-05 and now setsASPNETCORE_URLS=http://+:80, so the container listens on port 80. The standalone compose files were still mapping"80:8080"from a prior era when the image listened on 8080, leaving nothing on port 80 inside the container to answer the host port 80 traffic.Changes
standalone/docker-compose.yml:"80:8080"->"80:80"standalone/docker-compose-azure-sql-edge.yml: same fix (uses the sameregscale/regscale:latestimage)Not in this PR (intentionally)
standalone/atlas-deploy.yaml(k8s manifest) still hascontainerPort: 8080, but it referencesc2labs/atlasity:latest, which is a different image on a different release cadence thanregscale/regscale:latest. I haven't verified what port that image listens on today, so I'm leaving it alone for this PR. If it's still in use, it should be verified and updated in a follow-up; if it's stale legacy, it can be cleaned up.regscale/Dockerfile-- pin the listener port explicitly (already done viaASPNETCORE_URLS=http://+:80) and ensure all build variants stay consistent, so this drift doesn't recur silently.Test plan
standalone_regscale.py setup, changing this exact mapping from80:8080to80:80restored access to the UI onhttp://localhost, allowed admin authentication, and completed initial platform configuration.docker image inspect regscale/regscale:latestthat the current image setsASPNETCORE_URLS=http://+:80(listener port 80).standalone_regscale.py setupagainst the merged main produces a reachable UI without manual edits.