jj9987

User `postgres` is configured with ID 999 in the container. The docker entrypoint script configures the postgres data directories to be owned by that user, if container is started as root (but postgres is run as postgres user). https://github.com/docker-library/postgres/blob/master/15/bookworm/docker-entrypoint.sh#L59

That's normal PostgreSQL log at default level (LOG: indicates informative message). What's the exact error you are seeing?

What update did you do? What tag are you using?

PostgreSQL has a process, that you must follow for major version upgrades.

Seems like the user, that is connecting to the database, does not have the correct permissions. What have you done so far? How did you configure the database and the users?

Postgres doesn't change the permissions, unless it is run the first time (when it needs to initialize the data directory) even then it sets them to 775. 600 might not be enough for PostgreSQL data directory anyway. https://github.com/docker-library/postgres/blob/master/14/bullseye/docker-entrypoint.sh The owner can be unknown, because it is configured for the user ID that Postgres image runs as within the container. Just because host doesn't know the UID, doesn't mean it's broken. But it needs to match the userID, that the postgres process in Docker runs as. PUID and PGID don't do anything, they are specific to Linuxserver images, not Docker in general. It feels like something else is changing the permissions.

PostgreSQL upgrades aren't as easy as increasing the version. To do it properly, you have three options: 1) Dump all data from the old version, import it into the new version. 2) Go through the pg_upgrade process, which requires you to have binaries for both versions, but can be done in-place. 3) Using replication. Follow the official documentation on how to do each one of them, whichever suits you best: https://www.postgresql.org/docs/current/upgrading.html In case of containerized PostgreSQL, dump/import is probably the easiest to do, but will cause downtime.

Added the template for postgres 15. Postgres CLI tools default to the same database name as the user you are trying to connect with. Maybe your database has a different name?

pg_dumpall tries to dump the whole database instance (all databases) and needs root/superuser permissions. If you want to dump a single database, use pg_dump.

It's a password failure error. Have you tried resetting the password?

What are the errors you are seeing?

These logs are normal, nothing alarming. It says it is ready to accept connections, so could it be something else? Wrong IP perhaps?

Howdy Docker works by mounting host paths to container paths. These are called volumes. Check where /var/lib/postgresql/data is mounted to. Latest version of the template defaults to /mnt/cache/appdata/postgresql<version>, e.g. /mnt/cache/appdata/postgresql14. That directory either should not exist, be empty or only contain PostgreSQL own files.

Port 5432 is not WebUI, it is PostgreSQL TCP port. This container only runs the database engine itself. If you want a webUI, you need to find and deploy some other tool.

What version of psql are you using to connect to it? What error is psql giving? Server logs do not give very much information what the error is.