Sorry, when mapped to /tmp/servers.json (according to the doc), same thing ...
ms-alpine:~# ls -lh /tmp/
total 4K
drwxr-xr-x2 root root4.0K Sep 11 08:41 servers.json
Should not I run container with root ?
From: Dave Page
Sent: Thursday, Septembe
On Thu, Sep 10, 2020 at 11:35 AM Mickaël SALMON 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
>
> drwxrwxrwx3 *5050 5050 * 4.0K Sep 10 12:29 pgadmi
Same problem after changing permissions to parent directory :
$ rm -rf /root/pgadmin4/*
$ chown -R 5050:5050 /root/pgadmin4
$ chmod 777 /root/pgadmin4
$ ls -lh
drwxrwxrwx3 5050 50504.0K Sep 10 12:29 pgadmin4
This is weird, servers.json is created with root permissions, should no
On Thu, Sep 10, 2020 at 8:29 AM Mickaël SALMON wrote:
> Hi community,
>
> I have a problem mapping file *servers.json* with latest docker image.
>
> Here is how I run my container :
>
> docker run --name pgadmin4 --restart unless-stopped -p 80:80 -e
> 'PGADMIN_DEFAULT_EMAIL=XXX' -e 'PGADMIN_DEFAU
Hi community,
I have a problem mapping file servers.json with latest docker image.
Here is how I run my container :
docker run --name pgadmin4 --restart unless-stopped -p 80:80 -e
'PGADMIN_DEFAULT_EMAIL=XXX' -e 'PGADMIN_DEFAULT_PASSWORD=XXX' -v
/root/pgadmin4/servers.json:/pgadmin4/servers.jso