From: Dave Page <dpage@pgadmin.org> Sent: Thursday, September 10, 2020 12:39 To: Mickaël SALMON <ms@sylob.com> Cc: pgadmin-support@lists.postgresql.org <pgadmin-support@lists.postgresql.org> Subject: Re: problem with docker image
On Thu, Sep 10, 2020 at 11:35 AM Mickaël SALMON <ms@sylob.com> wrote:
Same problem after changing permissions to parent directory :
$ rm -rf /root/pgadmin4/*
$ chown -R 5050:5050 /root/pgadmin4
$ chmod 777 /root/pgadmin4
$ ls -lh
drwxrwxrwx 3 5050 5050 4.0K Sep 10 12:29 pgadmin4
This is weird, servers.json is created with root permissions, should not it be 5050 ?
Huh, I missed that earlier. According to that, servers.json is a directory. It should be a file (note the d at the front of the ACL).
Ownership doesn't really matter, as long as the file is readable by UID 5050, and all the parent directories also have read and execute permissions that allow UID 5050 to use them.
Typically, /root is not accessible to users other than root - and it should stay that way; create another directory somewhere to put the servers.json file in.
I suspect the container (which runs under UID 5050) cannot read files in /root on your host. The file has permissions that would allow that, but does the directory it's in?
