-
Notifications
You must be signed in to change notification settings - Fork 79
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
Cache has wrong permissions #194
Comments
Hi and thx for your Report. Sadly, I can't reproduce your error. Can you please post the Humhub version, Image version (Hash or Tag) and Conteiner-Config (docker-compose or docker-command you used to start). |
We are running HumHub 1.8.1 from the Here's our
|
It seems like this was our mistake. Somehow our permissions were all set to
Maybe running Anyways, sorry for the inconvenience. |
You should always |
very interesting. The thing with chmod is, that using it reliably requires the container-user to be root. This is true for most docker installations, but isn't for some container platforms like OpenShift or other enterprise Kubernetes distributions. I would like to avoid running chown on every startup, also because it can significantly increase bootup times on large volumes with many files. |
@mriedmann can you please reopen this. It's an issue with the container startup. The cache has the incorrect permissions initially.
We really just need |
In most cases the cache dir would reside in a bind-mount so it isn't lost on container recreation. But, we can add it to the "install" part of the entry-point if you think this is needed (https://github.com/mriedmann/humhub-docker/blob/master/docker-entrypoint.sh#L132) |
Our permissions somehow broke again, but this time it was the search which didn't work anymore:
Running the |
@mriedmann Not sure why you think the cache dir would be in a bind-mount? None of the example run commands or docker-compose files have In my testing the |
Our permissions keep breaking whenever I update to a new HumHub version. I think @timwsuqld is right and something about the migration resets the permissions. |
Is there any update on this issues please? I have encountered the same issue in my installations on OpenShift. |
k8s and openshift is its own beast. Currently we depend on the right to modify permissions to some dirs on startup. The problem here is that this issue and the issue that you might have are not exactly the same. You can try to add an emptyDir volume and mount it at |
I think it may be some mistake during the container startup or somewhere in a cronjob, because lots of thing are running as root there. Btw, I'm not sure, but this may possibly resolve the issue: #308 |
Hi, |
Just to mentioned that I encounter the same cache issue running the latest image. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
When trying to save settings (e.g. global time zone), the following error is shown:
The logs show this error:
Apparently the permission files are owned by root and are set to 644 so that the PHP process can not access them.
Did we do something wrong?
The text was updated successfully, but these errors were encountered: