[BUG] - Mealie docker compose will not load database on fresh install with custom username/password

[Andrew-T-Smith]

First Check

• This is not a feature request.
• I added a very descriptive title to this issue (title field is above this).
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the Mealie documentation, with the integrated search.
• I already read the docs and didn't find an answer.
• This issue can be replicated on the demo site (https://demo.mealie.io/).

What is the issue you are experiencing?

Using the following docker compose file
`version: '3.7'
services:
mealie:
image: ghcr.io/mealie-recipes/mealie:v3.0.2
container_name: mealie
restart: always
ports:
- "9925:9000"
volumes:
- /mnt/torrent/mealie/data:/app/data/
environment:
# Set Backend ENV Variables Here
ALLOW_SIGNUP: "false"
PUID: 1000
PGID: 1000
TZ: America/Indianapolis
BASE_URL: https://recipes.mydomain.co
# Database Settings
DB_ENGINE: postgres
POSTGRES_USER: ${MEALIE_POSTGRES_USER}
POSTGRES_PASSWORD: ${MEALIE_POSTGRES_PASS}
POSTGRES_SERVER: postgres
POSTGRES_PORT: 5432
POSTGRES_DB: mealie
depends_on:
- postgres

postgres:
container_name: postgres_mealie
image: postgres:15
restart: always
volumes:
- /mnt/torrent/mealie/pgdata:/var/lib/postgresql/data
environment:
POSTGRES_PASSWORD: ${MEALIE_POSTGRES_PASS}
POSTGRES_USER: ${MEALIE_POSTGRES_USER}
PGUSER: ${MEALIE_POSTGRES_USER}
healthcheck:
test: ["CMD", "pg_isready"]
interval: 30s
timeout: 20s
retries: 3`

with the .env file saying anything but
MEALIE_POSTGRES_USER=mealie MEALIE_POSTGRES_PASS=mealie

will cause the database to not find the database mealie. This is on a fresh install

Steps to Reproduce

1. Attempt to use docker compose with the above compose file and the above .env file changed in any way (add a number to the end of the username and password)

Please provide relevant logs

mealie error.txt

Mealie Version

No response

Deployment

Docker (Linux)

Additional Deployment Details

docker-compose

[lucasfijen]

Hey! I ran into the same issue when setting up, for me the fix was to add POSTGRES_DB: mealie to the postgres image as env variable.

This variable will make the postgres image create the database if it doesnt exist yet. I was getting db does not exist errors from mealie:)

Was also wondering if there is a reason the example is still on postgres 15, and whether 17 isnt also working.

Here is my working current example:

  mealie:
    image: ghcr.io/mealie-recipes/mealie:v3.0.2@sha256:448d56c5b41b668a8e2f0e435ade52ce6bd574d906d3e45eba1e9a1d05f844ff #
    container_name: mealie
    restart: always
    ports:
        - "9925:9000" #
    deploy:
      resources:
        limits:
          memory: 1000M #
    volumes:
      - ${CONFIGROOT}/mealie/data:/app/data/
    environment:
      # Set Backend ENV Variables Here
      ALLOW_SIGNUP: "false"
      PUID: ${PUID}
      PGID: ${PGID}
      TZ: ${TZ}
      BASE_URL: ${MEALIE_URL}
      # Database Settings
      DB_ENGINE: postgres
      POSTGRES_USER: ${MEALIE_DB_USERNAME}
      POSTGRES_PASSWORD: ${MEALIE_DB_PASSWORD}
      POSTGRES_SERVER: mealie_postgres
      POSTGRES_PORT: 5432
      POSTGRES_DB: mealie
    depends_on:
      mealie_postgres:
        condition: service_healthy

  mealie_postgres:
    container_name: mealie_postgres
    image: postgres:15@sha256:5ab68e212eab9cd4a16ecbf40d9449c88e1073abdca3ecc3aa5514d4a1af2ed0
    restart: always
    volumes:
      - ${CONFIGROOT}/mealie/postgres_data:/var/lib/postgresql/data
    environment:
      POSTGRES_USER: ${MEALIE_DB_USERNAME}
      POSTGRES_PASSWORD: ${MEALIE_DB_PASSWORD}
      PGUSER: ${MEALIE_DB_USERNAME}
      POSTGRES_DB: mealie
    ports:
      - 5432:5432
    healthcheck:
      test: ["CMD", "pg_isready", "-d", "mealie", "-p", "5432"]
      interval: 30s
      timeout: 60s
      retries: 5
      start_period: 30s

[lucasfijen]

Fixed with #5894

[michael-genson]

See above from @lucasfijen