Fix docker compose not finding .env file #29
Merged
Conversation
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
Docker Compose looks for .env in the compose file directory (.ingestkit/) but init creates .env in project root. Add --env-file .env flag to ensure the environment variables are loaded correctly. Fixes: POSTGRES_PASSWORD not set warning and postgres unhealthy error
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 the
POSTGRES_PASSWORDvariable not being loaded when runningingestkit server start.Problem
Docker Compose by default looks for
.envin the same directory as the compose file. Since the compose file is at.ingestkit/docker-compose.yaml, it looks for.ingestkit/.envbutinit --servercreates.envin the project root.Solution
Add
--env-file .envflag to docker compose commands so it explicitly loads the.envfile from the project root.Error Before Fix
Test Plan
ingestkit init --serverin a fresh directoryingestkit server start- should work without POSTGRES_PASSWORD warning