-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[bitnami/wordpress-nginx] The bitnami/wordpress-nginx:6.3.2-debian-11-r8 image is upgraded to bitnami/wordpress-nginx:6.5.2-debian-12-r3, but the container cannot be started. #65649
Comments
Could you provide more info about how are you deploying the container? |
Thanks for sharing the env. vars, that could help to reproduce the issue on our side. Could you please share how are you deploying the container? Just with |
It seems the issue appears when trying to connect to the database. How is this database deployed? Can you access it using another client? |
My database uses aws rds, other users can connect to the database |
|
Could you launch the container with |
Thank you very much for your answers. The problem has been solved. |
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/wordpress-nginx:6.5.2-debian-12-r3
What architecture are you using?
None
What steps will reproduce the bug?
The bitnami/wordpress-nginx:6.3.2-debian-11-r8 image is upgraded to bitnami/wordpress-nginx:6.5.2-debian-12-r3, but the container cannot be started.Container error
The text was updated successfully, but these errors were encountered: