Hey everyone,
I’ve deployed Eramba (Community Edition) in Kubernetes, and I’m encountering the following issue:
eramba needs to be able to access files inside its working directory, if this check fails then one or more files and/or directories are not owned by the process that runs apache. The easiest way to correct this is by using the chown command on linux for example "chown www-data:www-data eramba/ -R" in ubuntu. In Centos or Redhat apache typically runs as apache and therefore the command is likely to be different, for example: "chown apache:apache eramba/ -R
However, when I check the filesystem in the pod, I get the following output:
root@eramba-application-5b5745b777-5lsww:/var/www# ls -ltrh
drwxrwxrwt 1 www-data www-data 6 Sep 4 23:28 html
drwxr-xr-x 1 www-data www-data 17 Sep 24 12:31 eramba
It seems like the file permissions are already correct (owned by www-data), but the issue still persists. Any ideas on what might be going wrong?
Thanks in advance!
Hey everyone,
I’ve deployed Eramba (Community Edition) in Kubernetes, and I’m encountering the following issue:
However, when I check the filesystem in the pod, I get the following output:
It seems like the file permissions are already correct (owned by www-data), but the issue still persists. Any ideas on what might be going wrong?
Thanks in advance!