Closed LVoogd closed 3 years ago
@LVoogd thank you for reporting this issue. I will try to work on it ASAP.
@LVoogd I'm not able to reproduce it on minikube v1.16.0
(using Docker v20.10.2
for nodes) and Kubernetes v1.19.0
and Helm v3.5.4
.
Do you have more details about your Kubernetes setup? Also if you have any custom setup with security rules?
However, I believe if you set fsGroup
it should work.
So in the values file add the following:
podSecurityContext:
fsGroup: 1000
However, I believe if you set
fsGroup
it should work.So in the values file add the following:
podSecurityContext: fsGroup: 1000
I have tested this option and the internal H2 works now. It would be great if you update this into the template by default?
Updated: just submitted a PR for this #8
This issue has been fixed in the latest version v1.0.0, please use it and feel free to open the issue again if you still have it.
When I try to deploy this chart using the internal database a volume is created where the db is created and stored on. Tomcat does not seem to have the right permissions to access the created file on this volume.
Kubernetes version: 1.19 HELM version: 3.5.4
values.yaml
Partial stacktrace:
pod status:
Full log of the pod: