Re: pgAdmin in Docker: independent users storage

UPDATE:
I am sorry, of course I made a stupid mistake by using wrong command key
for environment variables. After changing it to "-e" pgAdmin4 does start in
SERVER mode. I also had to remove "-t" in order for it to bypass password
request.

Any ETA when version 3.3 will be released in the image?

Regards,
Vlad

пт, 14 сент. 2018 г. в 23:36, Vladimir Ryabtsev <greatvovan(at)gmail(dot)com>:

> Tried some of huggla/pgadmin-alpine images. I start it with
>
> docker run -it --rm -v VAR_param_SERVER_MODE=True -v VAR_email_server=
> user(at)domain(dot)com -v VAR_password_server=qwerty -p 5050:5050
> huggla/pgadmin-alpine:<tag>
>
> latest:
> does not work (but you mentioned it should not)
>
> 20180907-edge:
> reports "sudo: /usr/local/bin/sudo must be owned by uid 0 and have the
> setuid bit set" and exits.
>
> 20180829:
> reports "env: can't execute '/stop/stage1': Text file busy" and exits on
> one machine;
> launches version 3.2 in DESKTOP mode on another.
>
> 20180829-edge:
> reports "env: can't execute '/stop/stage1': Text file busy" and exits on
> one machine;
> launches version 3.2 in DESKTOP mode on another.
>
> 20180628:
> works on both machines and launches version version 3.0 in DESKTOP mode.
> What are these errors? Why won't it start in SERVER mode?
>
> Regards,
> Vlad
>
> пт, 24 авг. 2018 г. в 1:17, Henrik Uggla <Henrik(dot)Uggla(at)kristianstad(dot)se>:
>
>> 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(at)gmail(dot)com>
>> Skickat: den 24 augusti 2018 01:25:37
>> Till: pgadmin-support(at)lists(dot)postgresql(dot)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.
>>
>> How to do it?
>>
>> Best regards,
>> Vladimir
>>
>