-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Running as non-default user results in permission error on lock file #264
Comments
As a side note, I did manage to work around this by changing to the following process:
such that the process runs as my non-default user and the container's |
That looks like a bug on our part; we should probably |
I have the same problem running this command with postgres 9.1
|
@quiqueporta, support for running as an arbitrary user (#253) was added after See also, the Docker Hub readme (source) for the limitations. |
Did you try using --group-add=70 explicitly as well?
|
I have the same issue, use |
I can confirm adding |
I'm attempting to run the latest 9.6 container (have also tried the alpine container with the same result) with a non-default user. The data files are all created correctly by initdb, but the server itself never starts due to permission problems on
/var/run/postgresql
.Using the following command to start the container:
The following output is generated:
It would seem that while the data piece of allowing arbitrary users is working, the section of the Dockerfile at https://github.com/docker-library/postgres/blob/master/9.6/Dockerfile#L57 still requires
postgres
user or group, which cannot be assumed to exist on the host. Possible solution would be to make the directory world accessible, but I'm admittedly not positive what the security ramifications of doing so would be (though I suspect it's minimal given this is all inside the container)Or...I could just be doing something wrong. Any suggestions?
The text was updated successfully, but these errors were encountered: