Skip to content

container-volumes is not mounting to correct mount path #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cnukwas opened this issue Jul 29, 2020 · 0 comments
Open

container-volumes is not mounting to correct mount path #43

cnukwas opened this issue Jul 29, 2020 · 0 comments

Comments

@cnukwas
Copy link

cnukwas commented Jul 29, 2020

I have created following PersistentVolume and PersistentVolumeClaim definitions for our Shiny-proxy Kubernetes test environment and noticed that it's mounting to incorrect path instead of given NFS server path.

Any ideas on how to debug this issue?

PV

apiVersion: v1
kind: PersistentVolume
metadata:
name: nfs-pv
labels:
name: nfs-pv
spec:
persistentVolumeReclaimPolicy: Retain
storageClassName: manual
capacity:
storage: 500Mi
accessModes:
- ReadWriteMany
nfs:
server: nfs_host.com
path: /test
readOnly: false

PVC

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: nfs-pvc
namespace: sproxy
spec:
storageClassName: manual
accessModes:
- ReadWriteMany
resources:
requests:
storage: 200Mi

Then referred to above PVC as below in application.yaml for one of the applications.
container-volumes: ["nfs-pvc:/sproxy/data"]

The file system is shown as /dev/mapper/rootvg-homelv, instead of nfs_host.com:/test server and the path.

LEDfan pushed a commit that referenced this issue Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant