Let a reverse proxy name the container - #12
Merged
Conversation
The compose file pinned `container_name: nudo`. A proxy that generates its own container names — Coolify appends a per-deployment suffix — points its route at the name Compose would have generated, so pinning it leaves the backend unresolvable and the proxy answers 502 rather than reaching a container that is running and healthy. Dropping the key costs nothing: no script, doc, or workflow referred to the container by that name. The `docker run --name nudo` in the README is a separate path and still names its own container.
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.
What changed
container_name: nudofrom the Compose serviceWhy
Coolify appends a per-deployment suffix to service names (
nudo:main-ej0k0a09623vvgps4nke6ev5) and points its Traefik route at the name Compose generates.container_nameoverrides that naming and forces the container to be literallynudo, so the proxy's configured backend does not resolve.The result is a 502 with the app perfectly healthy — the container logs show
nudo is running — open the dashboard to finish setup dashboard=0.0.0.0:3000. The route exists; the backend behind it does not.Impact
Nothing referred to the container by that name — the
docker run --name nudoin the README and the release smoke test are a separate path and still name their own containers. Locally, Compose now auto-names itnudo-nudo-1;docker compose up -dandlocalhost:3000are unchanged.Validation
NUDO_SECRET_KEY=validation-only docker compose config --quietcontainer_nameis absent from the resolved configdocker compose config --imagesstill resolves only toghcr.io/loa212/nudo:latestgit diff --cached --check