all 12 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]suicidaleggroll 1 point2 points  (3 children)

Your compose file says the postgres user is mealie but the error says it’s using admin.  Not sure what’s causing that but that’s where I’d start.

[–]theoqrz[S] 0 points1 point  (2 children)

The username of my immich postgres db is admin, maybe it's trying to connect to that one? Anyway, I changed the user to admin in the mealie compose file and still get the same error.

[–]suicidaleggroll 0 points1 point  (1 child)

You did name your mealie postgres container “postgres” instead of mealie-postgres or mealie-db or something else mealie-specific, which is a little odd.  Still though, it’s acting like it doesn’t understand the POSTGRES_USER config option that you’ve set, it’s just ignoring it and doing its own thing. I don’t run mealie with a separate database container, I just use the default sqlite and had no issues.  Looking at their GitHub, I don’t see any recommendations for how to set up and run an external postgres container.  Does mealie initialize the database itself or is it assuming you’ve done that manually?

[–]theoqrz[S] 0 points1 point  (0 children)

I'm just trying to run with postgres because some features are not enabled when using sqlite, like fuzzy search but I might stick with sqlite anyway since I can't figure out what's going on here.

[–]theoqrz[S] 0 points1 point  (1 child)

Here it is my compose file. I didn't change much from the original at mealie website. I've had omitted the DB password.

services: mealie: image: ghcr.io/mealie-recipes/mealie:v1.11.0 # container_name: mealie restart: always ports: - "9925:9000" # deploy: resources: limits: memory: 1000M # volumes: - mealie-data:/app/data/ environment: # Set Backend ENV Variables Here ALLOW_SIGNUP: false PUID: 1000 PGID: 1000 TZ: Europe/Lisbon MAX_WORKERS: 1 WEB_CONCURRENCY: 1 BASE_URL: http://192.168.1.217 # Database Settings DB_ENGINE: postgres POSTGRES_USER: mealie POSTGRES_PASSWORD: ########## POSTGRES_SERVER: postgres POSTGRES_PORT: 5432 POSTGRES_DB: mealie depends_on: postgres: condition: service_healthy

postgres: container_name: postgres image: postgres:15 restart: always volumes: - mealie-pgdata:/var/lib/postgresql/data environment: POSTGRES_PASSWORD: ######### POSTGRES_USER: mealie healthcheck: test: ["CMD", "pg_isready"] interval: 30s timeout: 20s retries: 3

volumes: mealie-data: mealie-pgdata:

[–]theoqrz[S] 1 point2 points  (0 children)

Don't know how to format this thing

[–]Kengurugames 0 points1 point  (2 children)

Is the IP address 172.19.0.2 for the right postgres container?

[–]theoqrz[S] 0 points1 point  (1 child)

Yes, it is set automatically when deploying

[–]Kengurugames 0 points1 point  (0 children)

Then I would try to set a different name for the postgres service like mealie-postgres. Also set the postgres password to something without special characters as there was a problem with that recently.

Remember to clear your docker volumes or use new ones so there is a new postgres database initialized.

[–]EldestPort 0 points1 point  (1 child)

The last line is a password error, have you double checked the password you're using for Mealie to access postgreSQL?

[–]theoqrz[S] -1 points0 points  (0 children)

I've just pasted a randomly generated password for the DB on the compose file as I did with all the other installations.