We don't auto-apply ownership changes to hostPath volumes because that would allow, for example, a user to take over /etc. We've considered heuristics like "apply ownership if we make the directory" or "apply ownership if the path is under a flag-defined root", but none of them have been totally satisfying, and nobody has stepped up to prototype them
On Thu, Nov 9, 2017 at 2:32 AM, lppier <madst...@gmail.com> wrote: > I created a volume in linux as a certain user and mounted it using the > hostPath method. > My container is the tensorflow gpu default container, and I am able to see > the linux command prompt when I do : > > kubectl exec -it tf-gpu /bin/bash > > It logs into the container as root. > My issue now is that users would like to write to the mounted volume. I > found that this was not possible, unless I explicitly > chmod o+w -R volume > > which would beat the purpose of this volume being a user-specific volume > (other users should not be able to write or delete the items inside). > > Could I get some suggestions on how to proceed? > > Many thanks. > > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
