Closed Falven closed 6 months ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
I am trying to use static provisioning to mount an Azure Blob Container to a path on my singleuser server. I have set up a PV and PVC and the mounting is working. Additionally I have setup the following
securityContext
flags:Unfortunately, it seems that only the fsGid is respected. The mounted volume has the correct group, but is owned by
root
. These do not work either.Bug description
I need to be able to properly set the ownership of the mount so that I can read and write to it from
uid: 1000
. This is imperative as files created in the mount should inherit the ownership, allowing me to read/write to files that were created externally and uploaded to the Azure Blob Storage...How to reproduce
Expected behaviour
The mounted volume should be owned by whatever gid is set. In our case 1000 (jovyan).
Actual behaviour
The mounted volume is owned by
root
.Your personal set up
I created a standard installation of zero-to-jupyterhub with default authentication following the AKS guide.
I've tried setting up an initContainer to chown the drive, but it doesn't work reliably. The logs always say the permissions were changed but when I exec in most of the times they are not...