Skip to content
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

File-owner and/or -permissions in config-folder won't be adjusted at first run (Bug?) #1578

Open
n1smithy opened this issue Oct 16, 2024 · 0 comments

Comments

@n1smithy
Copy link

Hi @ all,

this is my first time I'm using wazuh, and I hope my containers run stablely now!

However: As a security-feature docker offers a userspace-remapping so docker-containers run outside of the host's userspace. But there's a little issue when using this feature.

The shared/persistent storaged folders/files must be chowned by root to fit in that userspace. Usually one sets all of the persistent files to the first UID and GID of the designated remapping-userspace. For example: the remap-userspace begins with UID/GID 100000:100000, then this would be the UID and GID for the remapped root-superuser. When running the container at it's first time, the shared files and folders should be automatically be set to them's right ownerships by the containers (remapped) root-user.

However, within wazuh's container-instances it's impossible to let the server write to the .../config/wazuh-dashboard/wazuh.yml-file because of wrong file-permissions/-ownership.

If there's a list of the right ownerships and permissions, one could at least easily change them manually.

Thanks for reading!

Greetings!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant