You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue:
CrashLoopBackOff when initializing the Master or Worker Nodes.
Because in wazuh master/worker init they want to chown to root:wazuh or 0:999 on etc/filebeat and some other files.
But the NFS is configured with root squash, so all files are owned by nobody:nobody or 65534:65534
And cannot be owned by root.
Same Issue #556 but they closed it by using nfs3 or non_root squash
Setup:
Issue:
CrashLoopBackOff when initializing the Master or Worker Nodes.
Because in wazuh master/worker init they want to chown to
root:wazuh
or0:999
onetc/filebeat
and some other files.But the NFS is configured with root squash, so all files are owned by
nobody:nobody
or65534:65534
And cannot be owned by root.
Same Issue #556 but they closed it by using nfs3 or non_root squash
non_root squash would be a security issue, see therefor (https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/4/html/security_guide/s2-server-nfs-noroot)
The text was updated successfully, but these errors were encountered: