-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Drupal cannot connect to database #75146
Comments
Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side. If you think that's not the case and want to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here. Your contribution will greatly benefit the community. Please feel free to contact us if you have any questions or need assistance. Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology. With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights. |
Hey Carlos, With that, line 100 in
whereas before 11.0.6, it has been expanded to
The remaining $-signs now crash the execution at that point. Using the container bitnami/drupal:11, but replacing the file just documentation purposes, the database array in my settings.php looks like this: $databases['default']['default'] = array (
'database' => 'bitnami_drupal',
'username' => 'bn_drupal',
'password' => 'aPassword',
'prefix' => '',
'host' => 'mariadb',
'port' => '3306',
'namespace' => 'Drupal\\Core\\Database\\Driver\\mysql',
'driver' => 'mysql',
'isolation_level' => 'READ COMMITTED',
); So you probably want to revert commit df18860 and find a better solution for the underlying problem. |
Thank you for bringing this issue to our attention. We appreciate your involvement! Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/drupal:11.0.9
What architecture are you using?
amd64
What steps will reproduce the bug?
create docker containers for mariadb and drupal as described in bitnami/drupal's readme
What is the expected behavior?
Containers will come up and connect providing a Drupal instance
What do you see instead?
Additional information
up to 11.0.5, everything worked fine. Starting with 11.0.6 the above behavior occurs
The text was updated successfully, but these errors were encountered: