You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 18, 2019. It is now read-only.
As an example, if the user has DATA_DIR set on the host machine and then tries to run docker-compose up -d on the broker, the DATA_DIR from the host machine will take precedence over any values in the .env file.
This is likely due to - DATA_DIR=${DATA_DIR:-} which is a tactic we use to suppress warnings from docker-compose (with docker-compose saying that it is setting environment variable to an empty string).
We should find ways to avoid the hosts environment from overriding these values, or at least mitigate it through namespacing.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As an example, if the user has DATA_DIR set on the host machine and then tries to run
docker-compose up -d
on the broker, the DATA_DIR from the host machine will take precedence over any values in the.env
file.This is likely due to
- DATA_DIR=${DATA_DIR:-}
which is a tactic we use to suppress warnings from docker-compose (with docker-compose saying that it is setting environment variable to an empty string).We should find ways to avoid the hosts environment from overriding these values, or at least mitigate it through namespacing.
The text was updated successfully, but these errors were encountered: