Closed zerowebcorp closed 5 months ago
I did find this as a workaround
initContainers:
- name: volume-permissions
image: busybox
command: [ 'sh', '-c', 'chmod -R g+rwX /bitnami' ]
volumeMounts:
- mountPath: /bitnami
name: data
Fix in v4.2.2
Describe the bug
When running on a bare metal k8s server and testing with a local volume mounted as hostPath, the bitnami non-root container is not able to access the PV even though the pv is created. The solution, as I understand is to use the
volumePermissions
init container. However, enabling this option throws an error.To Reproduce
Expected behavior
initContainer is created.
Error