Fix log permissions, HASHIDS env var generation, and the two errors that have been showing up since the v1.12.0 update #5324
Conversation
…r off
The v1.12.0 update comes with two breaking changes to the Docker image.
First error:
Creating migration table ...................................... 16.96ms DONE
INFO Loading stored database schemas.
database/schema/mysql-schema.sql .............................. 15.18ms FAIL
Process.php line 275:
The command "mysql --user="${:LARAVEL_LOAD_USER}" --password="${:LARAVEL_L
OAD_PASSWORD}" --host="${:LARAVEL_LOAD_HOST}" --port="${:LARAVEL_LOAD_PORT}
" --database="${:LARAVEL_LOAD_DATABASE}" < "${:LARAVEL_LOAD_PATH}"" failed.
Exit Code: 127(Command not found)
Working directory: /app
Output:
================
Error Output:
================
sh: mysql: not found
Second error:
Once the mysql client is added to the image, a second error shows up if encryption is not enabled, as is the case for many single-node deployments where the database is an internal-only service:
TLS/SSL error: SSL is required, but the server does not support it
Loki-101
changed the title
|
This PR has been renamed to reflect all current known issues with the image that are being addressed. The v1.12.0 update comes with two breaking changes to the Docker image. First error: INFO Loading stored database schemas. database/schema/mysql-schema.sql .............................. 15.18ms FAIL Process.php line 275: The command "mysql --user="${:LARAVEL_LOAD_USER}" --password="${:LARAVEL_L Exit Code: 127(Command not found) Working directory: /app Output:Error Output:sh: mysql: not found Second error: Once the mysql client is added to the image, a second error shows up if encryption is not enabled, as is the case for many single-node deployments where the database is an internal-only service: TLS/SSL error: SSL is required, but the server does not support it |
|
Solves #5521 |
1 participant
Tested on branch
v1.11.10v1.12.0