-
Notifications
You must be signed in to change notification settings - Fork 30
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
Deployment to rancher fails #1
Comments
Found something! Entering the container to check the permissions, it seems like the PVC is mounted correctly to Is it set somehow in the helm chart what the ownership of the PVCs are? I checked the mariadb PVC for comparison, and the mount is still owned by root, but the group is set to 1001 and the group also has write permissions. |
Thanks for the feedback! I will fix the permissions in the evening.
W dniu śr., 26.05.2021 o 14:22 Gustav Johansson ***@***.***>
napisał(a):
… Found something! Entering the container to check the permissions, it seems
like the PVC is mounted correctly to /opt/kimai/var but is owned by root,
whereas the user of the container is www-data, thus the "Permission
denied."
Is it set somehow in the helm chart what the ownership of the PVCs are?
I checked the *mariadb* PVC for comparison, and the mount is still owned
by root, but the group is set to 1001 and the group also has write
permissions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFLPUHFTWOLONZPH33QMKLTPTRXJANCNFSM45R4FK5A>
.
|
@neerdoc please try again |
That solved this issue! Thank you! I can now follow the instructions in the "Release Notes" of the helm chart and connect to my fresh kimai2 installation! Great work! I shall now continue and see if I can figure out how to leverage rancher's ingress (traefik by default) and let'sEncrypt certificates to access kimai externally. |
Trying to deploy the helm chart in a vanilla rancher installation.
values.yaml
.This results for me in:
of which everything except the pod from the image
kimai/kimai2:apache
works.kimai/kimai2:apache
is in a "Crashloopback" state, and examining the logs it shows that during deployment, just after it connects to the database the first time, it tries to create a folder named/opt/kimai/var/cache/prod
which fails 5 times with the same message: "In Kernel.php line 688: Unable to create the "cache" directory (/opt/kimai/var/cache/prod).". Next, it fails (which I assume is a follow-up problem) with the message: "/startup.sh: line 53: /opt/kimai/var/installed: Permission denied". It then states "Kimai2 ready" and goes into the Crashloopback state with continuing messages:Not sure where to start debugging...
The text was updated successfully, but these errors were encountered: