-
-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] /config/www/.env does not consume env_file directive correctly #262
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Why would you assume that a .env file inside the container would populate with the contents of a .env file passed to docker compose? The reason your container isn't starting up correctly is that you're using the wrong environment variables for the database username and password. |
I am getting the same issue. I was using DB_USER and DB_PASS, changed to DB_USERNAME and DB_PASSWORD as @M-Pepper was using. My environment has been running in Azure against an App Service for 2yrs and stopped working in the last 24-48hrs. Waiting for DB to be available Illuminate\Database\QueryException SQLSTATE[HY000] [1045] Access denied for user 'database_username'@'52.245.250.134' (using password: YES) (Connection: mysql, SQL: select table_name as at /app/www/vendor/laravel/framework/src/Illuminate/Database/Connection.php:829
37 /app/www/artisan:35 |
FYI: rolled container back to earlier version ... all working again. |
Same issue?
|
@flier268 no, quite a different issue. If running on Windows via WSL you may be running into the issue as described in MariaDB/mariadb-docker#331. |
Is there an existing issue for this?
Current Behavior
I'm using vault to generate custom .env files for my services that hold sensitive secrets and for quick rotation.
The bookstack
/config/www/.env
inside the container does not consume theenv_file
contents.Example compose configuration:
Example of
/opt/vault/env/.env.bookstack
:How the
/config/www/.env
file is created on container creation:Expected Behavior
Proper consumption of env_file declarations.
Steps To Reproduce
See above.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: