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

[J0rg10]

The issue still persist in v0.34.4.
For those wanting a quick workaround, use the extra volumes / mounts feature :

extraVolumeMounts:
  - name: vaultwarden-data
    mountPath: "/data"

extraVolumes:
  - name: vaultwarden-data
    persistentVolumeClaim:
      claimName: "vaultwarden-data"

## Broken : cause nested mounts
##storage:
##  existingVolumeClaim: 
##    claimName: "vaultwarden-data"
##    dataPath: "/data"
##    attachmentsPath: /data/attachments

[lkvrsfld]

hey all, setting "extraVolumeMounts" works - but then the normal created PVCs won't mount - see this example:

  # existingVolumeClaim:
  #     claimName: "vaultwarden-restored-pvc"
  #     dataPath: "/data"
  #     attachmentsPath: /data/attachments
  #     accessMode: "ReadWriteOnce"
  data:
    name: "vaultwarden-data"
    size: "10Gi"
    path: "/data"
    keepPvc: true
    accessMode: "ReadWriteOnce"
  attachments:
    name: "vaultwarden-attachments"
    size: "10Gi"
    path: "/attachments"
    keepPvc: true
    accessMode: "ReadWriteOnce"
extraVolumeMounts:
  - name: vaultwarden-data-bak
    mountPath: "/data_bak"
extraVolumes:
  - name: vaultwarden-data-bak
    persistentVolumeClaim:
      claimName: "vaultwarden-restored-pvc"

I just wanted to move the data from my old volume to newly created ones. the PVCs are created (data, attachment), but they aren't mounted - extraVolumeMounts seems to overwrite those fully.

[lkvrsfld]

please check #190 - it includes both fixes