Nuwan Goonasekera

@pcm32 This PR: https://github.com/galaxyproject/galaxy-helm/pull/396 should solve the container startup speed issue, but it's awaiting a merge of: https://github.com/CloudVE/galaxy-cvmfs-csi-helm/pull/16

Yes, it should it should be possible to use an `emptyDir` mount to create a container local mount?

Please query the namespace to check which persistent claims are not bound. Most likely, you will need to configure a storage class that supports ReadWriteMany, such as nfs, if you're...

Aah I see. You may have run into an issue with the cvmfs csi driver. Try restarting the cvmfs-csi daemonset, then restart the pods that use the pvcs. Also, can...

I think this message highlights the error: `no persistent volumes available for this claim and no storage class is set` Try setting a default storage class in your cluster: ```...

That's a dependency coming from here: https://github.com/CloudVE/galaxy-cvmfs-csi-helm/blob/a75a195396710bfc50dab3fb227330dea3a0c3a2/galaxy-cvmfs-csi/values.yaml#L38 So you'll need to set `cvmfs.cvmfscsi.cache.alien.pvc=nfs-csi`. Or alternatively, you can create a storage class named nfs.

My example was missing the last field: https://github.com/CloudVE/galaxy-cvmfs-csi-helm/blob/a75a195396710bfc50dab3fb227330dea3a0c3a2/galaxy-cvmfs-csi/values.yaml#L38 It should be set as: `--set cvmfs.cvmfscsi.cache.alien.pvc.storageClass=nfs-csi`

If you want to install the csi chart separately, you will need to uninstall the Galaxy chart first, as it already bundles the csi chart and you cannot have two...

It appears that none of your nfs storage classes are being provisioned. Which suggests that the nfs-provisioner is not correctly configured. This message confirms: `waiting for a volume to be...

Assuming this worked out. Please reopen if necessary.