-
Notifications
You must be signed in to change notification settings - Fork 218
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
NFS mount for data directory of postgresql 9.5 container #213
Comments
The benefit of
All over the place == all containers? You can make the directory world-writeable, or group '0' writeable (I think by default the processes are run under group 0). I'm not convinced this is a good recommendable default, though. |
as in if documentation can be updated with a better explanation? |
@praiskup |
Checked again -- atm. PostgreSQL processes are run as 'postgres:postgres', you you somehow have to set the permissions so the process can write to data directory. Other option is to change the user by |
@praiskup : I have been keeping an eye on PR #208. IIUC the outcome should be seamlessly attaching host machine volume to
Results are same with and without providing |
@navidshaikh have you added proper group ownership to /tmp/foo? ( |
|
Trying to share NFS mount from host machine, as data directory to postgresql 9.5 container
run command:
here
/srv/db2/cccp/
is NFS share mounted on the host system.NFS server exports a directory with config
/nfsshare *(rw,sync,no_subtree_check,all_squash,anonuid=0,anongid=0)
the docs mentions using
setfacl
command to work around with postgresql container dir ownership behavior, however while runningsetfacl
command as mentioned, it promptsOperation Not Permitted.
Note: Changing NFS server config to have uid=26 works for postgresql container, however, how does one manage UID/GID consistency all over the place then?
The text was updated successfully, but these errors were encountered: