Just stumbled across this whilst trying to boot the image in my orchestration system. It looks like the DB env vars in the docker-compose.yml file are ignored in favour of those in the .env.sample file copied over during compilation. I'm assuming that file is being loaded and overwriting the env vars passed in through docker, as echo $DB_HOST on the command line returns the correct one.
I'm not especially familiar with the setup, so I'm not sure if there's a correct way of remedying this, but perhaps the Dotenv library has an option for defaulting to the existing vars?
Just stumbled across this whilst trying to boot the image in my orchestration system. It looks like the DB env vars in the
docker-compose.yml
file are ignored in favour of those in the.env.sample
file copied over during compilation. I'm assuming that file is being loaded and overwriting the env vars passed in through docker, asecho $DB_HOST
on the command line returns the correct one.I'm not especially familiar with the setup, so I'm not sure if there's a correct way of remedying this, but perhaps the Dotenv library has an option for defaulting to the existing vars?