This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Replies: 2 comments 1 reply
-
That's totally right, I didn't think about that. I'll set the defaults to 33 |
Beta Was this translation helpful? Give feedback.
0 replies
-
This 9cb5104 should fix it |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
In my docker log I'm getting a:
after a docker pull since about 12h ago when accessing my kimai2 instance and the instance was inaccessible.
I think 99dea36#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557R254 could have done this.
I'm only reporting in case someone else has this too.
I couldn't fix this by just setting the permissions for the
/opt/kimai/var
or/opt/kimai/var/cache
manually, they were reset. Not even make them world writable did fix it, I just got a different error 500 (with no further error in docker log, I had to visit the kimai2 logs in the log directory).I could only fix this by setting the env vars to 33 (www-data), 1000 (www-kimai) didn't work for me:
All other files/dirs were already owned by
www-data
.Docker compose file (with passwords redacted)
Beta Was this translation helpful? Give feedback.
All reactions