Support thread for the pgadmin Docker template.

 

Application Name: pgadmin

Application Site: https://www.pgadmin.org/

Docker Hub: https://hub.docker.com/r/fenglc/pgadmin4/

Application Github: https://github.com/postgres/pgadmin4

Template Github: https://github.com/rroller/unraid-templates

 

Admins: Please configure  https://github.com/rroller/unraid-templates for use with CA. Thanks!

Thanks for your pgAdmin4 template. Do you have any plans to upgrade from pgAdmin4 version 2.1 to the latest 3.4?

When I open the webui, it asks me for my email and password. Unfortunately, i havent configured that anywhere. There is no email password configuration in the docker creation. Have anybody success using this? might as well use docker command.

When I open the webui, it asks me for my email and password. Unfortunately, i havent configured that anywhere. There is no email password configuration in the docker creation. Have anybody success using this? might as well use docker command.

https://hub.docker.com/r/fenglc/pgadmin4/

Sent via telekinesis

7 hours ago, Squid said:

https://hub.docker.com/r/fenglc/pgadmin4/

Sent via telekinesis
 

Thank you very much.

Will this be updated to the new version?

Quote

You are currently running version 2.1 of pgAdmin 4, however the current version is 4.10.

 

Edited July 6, 20196 yr by remati

I'm having trouble setting up pg_restore.

There is no pg_restore bin that I can find, so I pulled a copy from the Linux (other version) EnterpriseDB tar.gz archive for Postgres10. I used the Postgres10 docker (by postgres) to ensure the pg_restore matched the PostgreSQL version. I placed the pg_restore bin in the /appdata/pgadmin/config/storage/pgadmin4 which I found mapped to "/" in pgadmin4 (for some reason the additional paths I setup in the docker configuration are not working).

In pgadmin4, I set the File > Preferences > Paths > Binary Paths all to "/" since that is there I placed the pg_restore bin.

When I setup a server and attempt to restore my .backup file the process starts and runs infinitely. Upon checking the logs, I get the following message:

Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/pgadmin4/pgadmin/misc/bgprocess/process_executor.py", line 312, in execute
command, stdout=PIPE, stderr=PIPE, stdin=None, **kwargs
File "/usr/local/lib/python3.6/subprocess.py", line 709, in __init__
restore_signals, start_new_session)
File "/usr/local/lib/python3.6/subprocess.py", line 1344, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/pg_restore': '/pg_restore'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/pgadmin4/pgadmin/misc/bgprocess/process_executor.py", line 533, in <module>
execute()
File "/usr/local/lib/python3.6/site-packages/pgadmin4/pgadmin/misc/bgprocess/process_executor.py", line 349, in execute
info = _log_exception()
File "/usr/local/lib/python3.6/site-packages/pgadmin4/pgadmin/misc/bgprocess/process_executor.py", line 70, in _log_exception
fp.write('EXCEPTION::\n{0}'.format(res))
TypeError: a bytes-like object is required, not 'str'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/pgadmin4/pgadmin/misc/bgprocess/process_executor.py", line 535, in <module>
_log_exception()
File "/usr/local/lib/python3.6/site-packages/pgadmin4/pgadmin/misc/bgprocess/process_executor.py", line 70, in _log_exception
fp.write('EXCEPTION::\n{0}'.format(res))
TypeError: a bytes-like object is required, not 'str'

Obviously, pgadmin4 can't find my pg_restore binary, or something else is wrong. I'd appreciate any help in restoring my .backup so I can store and serve it from unraid.

Cheers,

Edited January 17, 20206 yr by njdowdy
clarity

Admins, can you remove this application? The dockerhub link is gone, the container ships with a username/password already configured and the only way to obtain the original username/password for configuration is in the dead dockerhub url.

dockerHub is having issues right now.  Try again later (ie: pretty much anything you search for on dockerHub will now return a 404)

 

https://status.docker.com/pages/history/533c6539221ae15e3f000031