When you launch with docker you'd use something like the following on the command line to map the directory containing session data and configs to the host:
-v "/private/var/lib/pgadmin:/var/lib/pgadmin"
The first path being the one on the host, the second being the path in the container to remap.
Yes, put the Sqlite file (by default named pgadmin4.db) on a shared persistent volume on f ex Rancher-NFS. I don't know which Docker image you are using but if you use mine (huggla/pgadmin-alpine), then you're able to change the location of the sqlite file inside the container by setting the environment variable VAR_param_SQLITE_PATH.
Cheers, Henrik ________________________________________ Från: Vladimir Ryabtsev <greatvovan@gmail.com> Skickat: den 24 augusti 2018 01:25:37 Till: pgadmin-support@lists.postgresql.org Ämne: pgAdmin in Docker: independent users storage
Hi,
I am running pgAdmin in Rancher, which means the container, in some circumstances, can be moved to another host. In this case I lose all users as well as users' settings (set-up server connections), which in turn implies I have to re-create users and they have to set up everything again.
To make pgAdmin tolerant to restarts and moves, I guess I need to put it's database on some volume that would be mounted to container on any host.