I would expect the Azure volume to *do the right thing* with respect to setting UID/GID (since it can't be changed, and realistic apps expect it to be certain values, then those apps can't run on azure unless the plugin can solve the problem). Parameterizing the UID/GID may not be the right path, it might be something the security setup should decide.
On Mon, Apr 4, 2016 at 11:18 AM, Diego Spinola Castro <[email protected]> wrote: > Ccing the list > > Em 4 de abr de 2016 12:02 PM, "Diego Spinola Castro" > <[email protected]> escreveu: >> >> Sorry, you are right, files can't get other ownership than default >> (uid,gid) underneath the mount point. >> As the root is mounting, so it owns the files, pods can write because >> file_mode and dir_mode are 0777 >> >> 2016-04-04 11:45 GMT-03:00 Clayton Coleman <[email protected]>: >>> >>> At the mount point, or anywhere underneath the mount point? >>> >>> On Mon, Apr 4, 2016 at 9:39 AM, Diego Spinola Castro >>> <[email protected]> wrote: >>> > Azure file plugin doesn't support Unix Permissions, so a pod can't >>> > manage >>> > file ownership at a mountpoint. This is a issue for PostgreSQL images, >>> > which >>> > complains if don't own the files. One alternative is to pass UID,GUID >>> > parameters at the mount, ex: >>> > >>> > mount -t cifs //ENDPOINT /MOUNTPOINT \ >>> > -o vers=3.0,user=USER,password=PASS,\ >>> > UID=<pod_user>,\ >>> > gid=<pod_supplemental_group>,\ >>> > dir_mode=0777,\ >>> > file_mode=0777 >>> > >>> > Is possible to have this or a similar solution ? >>> > >>> > >>> > Diego >>> > >>> > _______________________________________________ >>> > dev mailing list >>> > [email protected] >>> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>> > >> >> > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > _______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
