Using storage.existingVolumeClaim in v0.31.1 can't find existing attachments.

[se-jaeger]

Using storage.existingVolumeClaim mounts the actual attachments into /data/attachments/attachments, resulting in Bitwarden not finding the attachment files.

I'm suspecting that the second mount of vaultwarden-data is too much and causes some kind of 'recursion'

vaultwarden/charts/vaultwarden/templates/_podSpec.tpl

Lines 123 to 127 in 1bb422c

	volumeMounts:
	- name: vaultwarden-data
	mountPath: {{ default "/data" .dataPath }}
	- name: vaultwarden-data
	mountPath: {{ default "/data/attachments" .attachmentsPath }}

I'm using the latest version 0.31.1.

[ntcong]

oh I saw the problem with existingVolumeClaim, will try to fix it in a PR