Ghost wont start, Hostname mysql and Ghost directory issues

[hurley-code]

Name and Version

bitnami/ghost

What architecture are you using?

amd64

What steps will reproduce the bug?

1. In Unraid v6.12.4
2. mariadb container already in use, container hostname is mariadb
3. setup a database for ghost with a user and a password
4. Set the environment variables correctly in the Ghost template
5. deploy

What is the expected behavior?

The docker container installs and starts up.

What do you see instead?

The container will not start. Container log shows:

ghost 17:49:31.76 INFO  ==> Configuring libnss_wrapper
ghost 17:49:31.78 INFO  ==> Validating settings in MYSQL_CLIENT_* env vars
ghost 17:49:31.81 WARN  ==> Hostname mysql could not be resolved, this could lead to connection issues
ghost 17:49:31.81 INFO  ==> Ensuring Ghost directories exist
mkdir: cannot create directory '/bitnami/ghost': Permission denied

[hurley-code]

Oh and yes, they are both on the same proxy docker network

[carrodher]

Bitnami containers are designed to operate as non-root by default. Consequently, any files or directories used by the application should be owned by the root group, as the random user (1001 by default) is a member of this root group. To ensure proper permissions, you'll need to adjust the ownership of your local directory accordingly.

For more comprehensive information about non-root containers and their significance for security, you can explore the following resources:

• Why non-root containers are important for security
• Use Non-Root Containers
• Work With Non-Root Containers for Bitnami Applications
• Running non-root containers on Openshift

These references provide valuable insights into the best practices and considerations when working with non-root containers in Bitnami applications.

[github-actions[bot]]

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.

[github-actions[bot]]

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.