rsync permission denied (13) zammad-init container

[drabui]

Is this a request for help?:

yes

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

bug report?

Version of Helm and Kubernetes:

Kubernetes 1.20.5
Helm 3.5.4

What happened:

Zammad-init container is throwing permission denied errors

What you expected to happen:

working zammad pods

How to reproduce it (as minimally and precisely as possible):

I created persistentvolume
then used
helm repo add zammad https://zammad.github.io/zammad-helm
helm upgrade --install zammad zammad/zammad --namespace=zammad -f values.yml (cause I added the persistentVolume)

Anything else we need to know:

All I did was using the commands (https://docs.zammad.org/en/latest/install/kubernetes.html) then created a pv.yaml with this content and used the storageclassname in the value.yaml

apiVersion: v1
kind: PersistentVolume
metadata:
name: pv1
spec:
capacity:
storage: 15Gi
accessModes:
- ReadWriteOnce
hostPath:
path: /opt
storageClassName: pv1

and then the zammad-0 pod log throws permission denied (13) errors for /opt/zammad.
Since I'm very new to kubernetes and helm it could be very likely that I just don't know what I'm doing and my configuration fucks up things or that I'm missing something how to get zammad via helm working so please bare with me.

[drabui]

after solving the problem I'm now getting errors with the postgresql container

=> PG::ConnectionBad could not translate host name "zammad-postgresql" to address: temporary failure in name resolution

even though postgresql.enabled is true