Unable to modify owner of network volume
Hey all, I'm attempting to create a network volume and mount it to
/home inside the pod, attempting to create a user home dir. However, I am unable to change the owner away from root.13 Replies
Hey, are you able to use the root user and the default mountpoint? I'm interested in your choice of using
/home?Hey! We could likely make root user and default mountpoint work with our training, but it wouldn't work for dev environments.
We generally don't like to use
root user inside our containers.
We use /home inside our dev environment containers though. We build up an environment our researchers and devs are familiar with, with the stipulation that their user is <our-company's-generic-user> home dir is /home/<our-company's-generic-user> and not /home/<individual-user> . This works great with AWS and EBS volumes and creates a persistant home dir for users.
BTW we utilize dstackOur Pods are Docker containers, if it's not too much of a hassle does modifying your Dockerfile to set
USER <generic name> before the final CMD work? I'm not 100% sure on the actual effect of this just yet, I can test it out for you in a minute here.I hope that makes sense lol I can't disclose details or how much we'd likely be spending until NDAs are in place.
Yeah we do that
Set the user, I mean
I understand! Does setting the user not work? You might have to do the effort of making the user dir, giving it all the right perms, etc by yourself unless you did
RUN useradd ...If I mount the network volume somewhere else, it's all fine. But then obviously my user's home dir isn't persistent since it's not on the network volume
OH! I understand now, okay sorry I got confused.
No worries!
We run a mono repo, our build is huge...a base build for a dev to "work with" is like hundreds of gigs, so we can't be pulling and building every day, you know?
Definitely, I'm not sure this specific usecase is possible just because of the permissions issue but I'll check with someone else in a few minutes here.
Beautiful thanks. Maybe a feature request. I can't be the only one who'd want to change permissions on my volume mount away from
root
A bit more testing here and I find network volume behaviour strange. Maybe someone can clarify what's going on here.
- I'll mount the network volume to a more normal place, say /data/mount . Whatever user you ssh into the container as, is who the owner is? This is weird. ie, if I ssh as root , it's owned by root. If I ssh as <my-container-user> it's now owned by that user
- I can't properly change permissions on files on the network mount. It applies the same permissions across owner, group and everybody and I can't set different permissions for these.
Any insights to this?Not yet, let me ask around for clarity but I'm not sure if this is behavior we can quickly change.
What you’re seeing is expected behavior. I believe the underlying volume system remaps UID/GID dynamically based on the active user session, so ownership can appear different depending on who’s accessing the volume. Unfortunately, it’s a limitation for now that you can’t change the owner of files on the mounted network volume
Thanks @yhlong00000 . What about changing permissions then? That behaviour is also unexpected.