Fix: Add explicit network for Dokploy deployment#34
Open
bsqgm wants to merge 1 commit intocoollabsio:mainfrom
Open
Fix: Add explicit network for Dokploy deployment#34bsqgm wants to merge 1 commit intocoollabsio:mainfrom
bsqgm wants to merge 1 commit intocoollabsio:mainfrom
Conversation
…te a shared network by default, causing nginx to fail resolving the 'browser' hostname. Explicitly define a bridge network to ensure service discovery works. Fixes container DNS resolution error: "host not found in upstream 'browser'"
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.
Problem
When deploying with Dokploy, nginx fails to start with error:
[emerg] host not found in upstream "browser"
Root Cause
Dokploy's network isolation prevents automatic service discovery between containers.
Solution
Add explicit
openclaw-netbridge network to both services.Testing