docs: Adds warning for env injection in docker-compose#131
Merged
Siumauricio merged 2 commits intoDokploy:mainfrom Feb 16, 2026
Merged
docs: Adds warning for env injection in docker-compose#131Siumauricio merged 2 commits intoDokploy:mainfrom
Siumauricio merged 2 commits intoDokploy:mainfrom
Conversation
- Updated the documentation to specify two methods for injecting environment variables into containers: using the `env_file` option to load all variables or referencing specific variables with the `${VAR_NAME}` syntax.
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
2 participants
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.
This PR updates the documentation to make it clear that environment variables set in the Dokploy UI are not automatically injected into containers, unlike commercial alternatives. The has been widely confusing:
This docs change serves as a temporary solution to the above confusion, allowing users can find an answer on the official docs rather than hunting down closed GitHub issues/discussions. However, a complete fix should include:
docker-composefile (this is already done for Traefik labels, so I'm unsure why it couldn't be done here)Both of which have been suggested in the issues listed above.
Screenshot of docs fix: