Error creating filer server

[ghost]

Name and Version

bitnami/seaweedfs:latest

What architecture are you using?

amd64

What steps will reproduce the bug?

1. I created a docker compose with the nodes.
2. in node filer add this command: filer -master=main-node:9333 -ip=filer-node

What is the expected behavior?

The server filer created

What do you see instead?

I0626 16:13:50.961777 filer_server.go:171 default to create filer store dir in ./filerldb2
I0626 16:13:50.969043 leveldb2_store.go:42 filer store leveldb2 dir: ./filerldb2
F0626 16:13:50.969145 configuration.go:25 failed to initialize store for leveldb2: Check Level Folder ./filerldb2 Writable: stat ./filerldb2: no such file or directory

Additional information

I believe that you missed creating the line RUN mkdir -p /data/filerldb2 which is made by the imagen chrislusf/seaweedfs.

[carrodher]

Could you check the permissions of the local directory being mounted into the container?
Please note that 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.

[ghost]

I must to create my own configuration file to change default folder and add it with a volume. But I expect that this image can create all cluster to easy PoC without adding additional configuration.

[github-actions]

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]

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.