Mealie with Docker Compose
Mealie is a self hosted recipe manager, meal planner and shopping list with a RestAPI backend and a reactive frontend built in Vue for a pleasant user experience for the whole family. In the project's words: Mealie README (About The Project) checked 2026-09-23
Runs on: amd64, arm64 from each image's registry manifest, checked 2026-09-30; a CPU counts only if every image has a build for it. Image by image
Add Mealie to the builder to use your own domain and combine it with other apps in one file.
What Mealie needs
Only figures Mealie's own documentation publishes, each linked to the page it is on. Where the project gives no number, this page does not invent one.
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | The project publishes no figure | |
| No minimum is published. The official compose file caps the container at 1000M, and the docs recommend an explicit limit because Python can pre-allocate far more memory than it needs on a machine with a lot of RAM. Source: Mealie docs: Installation, SQLite (Recommended) checked 2026-09-23 | ||
| CPU | The project publishes no figure | |
| No speed or core count. Images exist for linux/amd64 and linux/arm64 only: 32-bit ARM is not supported, so a Raspberry Pi needs a 64-bit OS. Source: Mealie docs: Installation Checklist (Docker, 32bit Support) checked 2026-09-23 | ||
| Disk | The project publishes no figure | |
Which hardware Mealie has images for
Read from each image's manifest list in its registry (anonymous, read-only) when this page was built. An app counts for a CPU only if every one of its images lists it.
With SQLite, the default
- x86-64 PC or NAS (
linux/amd64): every image has a build. - Raspberry Pi 4/5, 64-bit OS (
linux/arm64): every image has a build. - Raspberry Pi 3 or Zero 2 W, 32-bit OS (
linux/arm/v7): no image formealie. No image for this hardware; the builder leaves the app out.
| Service | Image | Platforms in the manifest | Digest | Registry | Checked |
|---|---|---|---|---|---|
mealie | ghcr.io/mealie-recipes/mealie:v3.27.0 | arm64, amd64 | sha256:ba24b88462380fb59a6c7d04c6d9e607e0b6b04e31306592181186bcdab1952b | ghcr.io | 2026-09-25 |
With PostgreSQL
- x86-64 PC or NAS (
linux/amd64): every image has a build. - Raspberry Pi 4/5, 64-bit OS (
linux/arm64): every image has a build. - Raspberry Pi 3 or Zero 2 W, 32-bit OS (
linux/arm/v7): no image formealie. No image for this hardware; the builder leaves the app out.
| Service | Image | Platforms in the manifest | Digest | Registry | Checked |
|---|---|---|---|---|---|
mealie | ghcr.io/mealie-recipes/mealie:v3.27.0 | arm64, amd64 | sha256:ba24b88462380fb59a6c7d04c6d9e607e0b6b04e31306592181186bcdab1952b | ghcr.io | 2026-09-25 |
postgres | postgres:17 | amd64, arm/v5, arm/v7, arm64, 386, ppc64le, riscv64, s390x | sha256:d74eeac9a635390a49bc21bd49fccd973de707e2a53a76ac49b552b8712ec46f | registry-1.docker.io | 2026-09-30 |
docker-compose.yml
Mealie's docs recommend SQLite and also publish a PostgreSQL compose file: PostgreSQL "might be considered if you need to support many concurrent users", and some features, such as fuzzy search, only work on PostgreSQL. Choose before the first start. Source: Mealie docs: Installation, PostgreSQL docker-compose.yaml checked 2026-09-30
With SQLite, the default
This is exactly what the builder writes for Mealie alone on example.org: the official definition with its published ports removed and Caddy added in front. The time zone is Etc/UTC here; the builder uses your browser's.
# docker-compose.yml built at dankhost.com for: Mealie # Each app block is its official compose definition. Only the names were prefixed with # the app slug (services, containers, volumes, bind folders, .env variables) so any set of # apps can share one file; other differences are listed under "Changed:" in each block. # Only Caddy publishes ports. Secrets live in .env next to this file. services: # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ---- # Source: https://caddyserver.com/docs/running (checked 2026-09-23) # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23) # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly. caddy: image: "caddy:2" container_name: "caddy" restart: "unless-stopped" ports: - "80:80" - "443:443" - "443:443/udp" volumes: - "./caddy:/etc/caddy" - "caddy-data:/data" - "caddy-config:/config" networks: proxy: ipv4_address: "172.30.0.2" # ---- Mealie (recipes.example.org) ---- # Source: https://docs.mealie.io/documentation/getting-started/installation/sqlite/ (checked 2026-09-23) # Source: https://docs.mealie.io/documentation/getting-started/installation/installation-checklist/ (checked 2026-09-23) # Changed: Removed the documented '9925:9000' port; Caddy reaches mealie:9000 on the proxy network. # BASE_URL is your address instead of the documented example address mealie.yourdomain.com; TZ is your browser's time zone instead of the example America/Anchorage. mealie: image: "ghcr.io/mealie-recipes/mealie:v3.27.0" container_name: "mealie" restart: "always" deploy: resources: limits: memory: "1000M" volumes: - "mealie-data:/app/data/" environment: ALLOW_SIGNUP: "false" PUID: "1000" PGID: "1000" TZ: "Etc/UTC" BASE_URL: "https://recipes.example.org" networks: proxy: {} networks: # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact. # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's # ipv4_address and in every trusted-proxy value to a free 172.x.0 range. proxy: ipam: config: - subnet: "172.30.0.0/24" ip_range: "172.30.0.128/25" gateway: "172.30.0.1" volumes: caddy-data: caddy-config: mealie-data:
With PostgreSQL
This is what the builder's code writes for Mealie alone on example.org from the project's PostgreSQL setup (the builder on the front page still writes the SQLite version, so copy this one from here): the official definition with its published ports removed and Caddy added in front. The time zone is Etc/UTC here; the builder uses your browser's. Every ${VARIABLE} is defined in the .env below.
# docker-compose.yml built at dankhost.com for: Mealie # Each app block is its official compose definition. Only the names were prefixed with # the app slug (services, containers, volumes, bind folders, .env variables) so any set of # apps can share one file; other differences are listed under "Changed:" in each block. # Only Caddy publishes ports. Secrets live in .env next to this file. services: # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ---- # Source: https://caddyserver.com/docs/running (checked 2026-09-23) # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23) # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly. caddy: image: "caddy:2" container_name: "caddy" restart: "unless-stopped" ports: - "80:80" - "443:443" - "443:443/udp" volumes: - "./caddy:/etc/caddy" - "caddy-data:/data" - "caddy-config:/config" networks: proxy: ipv4_address: "172.30.0.2" # ---- Mealie (recipes.example.org) ---- # Source: https://docs.mealie.io/documentation/getting-started/installation/sqlite/ (checked 2026-09-23) # Source: https://docs.mealie.io/documentation/getting-started/installation/installation-checklist/ (checked 2026-09-23) # Source: https://docs.mealie.io/documentation/getting-started/installation/postgres/ (checked 2026-09-30) # Source: https://hub.docker.com/_/postgres (checked 2026-09-30) # Changed: Removed the documented '9925:9000' port; Caddy reaches mealie:9000 on the proxy network. # BASE_URL is your address instead of the documented example address mealie.yourdomain.com; TZ is your browser's time zone instead of the example America/Anchorage. # Uses the docs' PostgreSQL compose file: DB_ENGINE and the POSTGRES_ variables on mealie, mealie waiting for a healthy database, and a postgres service running postgres:17 (the major version the docs pin) with their pg_isready healthcheck. # The documented password 'mealie' (POSTGRES_PASSWORD on both services) is replaced by DB_PASSWORD, a random secret in .env; the documented user and database name, mealie, are kept. # The documented container_name 'postgres' becomes mealie-postgres. mealie still reaches it as postgres (POSTGRES_SERVER), on the internal network only: the database publishes no port and is not on the proxy network. # The mealie image stays at v3.27.0, as in the SQLite version; the PostgreSQL page showed v3.28.0 when checked. mealie: image: "ghcr.io/mealie-recipes/mealie:v3.27.0" container_name: "mealie" restart: "always" deploy: resources: limits: memory: "1000M" volumes: - "mealie-data:/app/data/" environment: ALLOW_SIGNUP: "false" PUID: "1000" PGID: "1000" TZ: "Etc/UTC" BASE_URL: "https://recipes.example.org" DB_ENGINE: "postgres" POSTGRES_USER: "mealie" POSTGRES_PASSWORD: "${MEALIE_DB_PASSWORD}" POSTGRES_SERVER: "postgres" POSTGRES_PORT: "5432" POSTGRES_DB: "mealie" depends_on: mealie-postgres: condition: "service_healthy" networks: proxy: {} mealie-backend: {} mealie-postgres: image: "postgres:17" container_name: "mealie-postgres" restart: "always" volumes: - "mealie-pgdata:/var/lib/postgresql/data" environment: POSTGRES_PASSWORD: "${MEALIE_DB_PASSWORD}" POSTGRES_USER: "mealie" PGUSER: "mealie" POSTGRES_DB: "mealie" healthcheck: test: - "CMD" - "pg_isready" interval: "30s" timeout: "20s" retries: 3 networks: mealie-backend: aliases: - "postgres" networks: # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact. # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's # ipv4_address and in every trusted-proxy value to a free 172.x.0 range. proxy: ipam: config: - subnet: "172.30.0.0/24" ip_range: "172.30.0.128/25" gateway: "172.30.0.1" mealie-backend: internal: true volumes: caddy-data: caddy-config: mealie-data: mealie-pgdata:
Caddyfile save as caddy/Caddyfile
Caddy gets and renews the HTTPS certificate for recipes.example.org by itself once the DNS record points at your server and ports 80 and 443 reach it.
# Caddyfile built at dankhost.com. Save it as ./caddy/Caddyfile next to docker-compose.yml.
# Caddy gets and renews a Let's Encrypt certificate for each name below by itself,
# once the DNS records point at this server and ports 80 and 443 reach it.
# Mealie
recipes.example.org {
reverse_proxy mealie:9000
}
.env
With SQLite, the default
Mealie needs no secret here; the builder adds nothing you have to fill in by hand.
# .env for Mealie, from dankhost.com/app/mealie/. Nothing here is secret. # Keep this file private (chmod 600). # None of the chosen apps needs a variable here.
With PostgreSQL
The secret is left blank here on purpose: a password printed on a public page is the same for everyone who copies it. Fill it with random letters and digits as in How to run it.
# .env for Mealie, from dankhost.com/app/mealie/. Fill the blank secret before starting. # Keep this file private (chmod 600). # Mealie # 32 random letters and digits, for example from: tr -dc A-Za-z0-9 </dev/urandom | head -c 32 MEALIE_DB_PASSWORD=
Changes from the official file
Besides prefixing every service, container, volume, folder and variable with mealie (so any set of apps can share one file), these are all the differences from what the project documents:
With SQLite, the default
- Removed the documented '9925:9000' port; Caddy reaches mealie:9000 on the proxy network.
- BASE_URL is your address instead of the documented example address mealie.yourdomain.com; TZ is your browser's time zone instead of the example America/Anchorage.
Notes for Mealie behind the proxy
- Mealie starts with a default account: log in as changeme@example.com with the password MyPassword (both from Mealie's installation checklist) and change them at once, because anyone who finds the address can use them until you do.
- ALLOW_SIGNUP is "false" as documented, so nobody can register; invite other people from the admin pages.
- The image is pinned to v3.27.0, the version the docs gave on the checked date. The Mealie team advises a fixed version tag and reading the release notes before you raise it.
With PostgreSQL
- Removed the documented '9925:9000' port; Caddy reaches mealie:9000 on the proxy network.
- BASE_URL is your address instead of the documented example address mealie.yourdomain.com; TZ is your browser's time zone instead of the example America/Anchorage.
- Uses the docs' PostgreSQL compose file: DB_ENGINE and the POSTGRES_ variables on mealie, mealie waiting for a healthy database, and a postgres service running postgres:17 (the major version the docs pin) with their pg_isready healthcheck.
- The documented password 'mealie' (POSTGRES_PASSWORD on both services) is replaced by DB_PASSWORD, a random secret in .env; the documented user and database name, mealie, are kept.
- The documented container_name 'postgres' becomes mealie-postgres. mealie still reaches it as postgres (POSTGRES_SERVER), on the internal network only: the database publishes no port and is not on the proxy network.
- The mealie image stays at v3.27.0, as in the SQLite version; the PostgreSQL page showed v3.28.0 when checked.
Notes for Mealie behind the proxy
- Mealie starts with a default account: log in as changeme@example.com with the password MyPassword (both from Mealie's installation checklist) and change them at once, because anyone who finds the address can use them until you do.
- ALLOW_SIGNUP is "false" as documented, so nobody can register; invite other people from the admin pages.
- The image is pinned to v3.27.0, the version the docs gave on the checked date. The Mealie team advises a fixed version tag and reading the release notes before you raise it.
- Mealie's own in-app restore (Settings > Admin Settings > Backups) needs its database user to be a PostgreSQL superuser; the docs give ALTER USER mealie WITH SUPERUSER for that. Here mealie is POSTGRES_USER, which the postgres image creates as a superuser, so nothing needs changing.
How to run it
With SQLite, the default
- At your DNS provider, add an A record named
recipeson your domain pointing at the server's public IP address, and forward TCP 80, TCP 443 and UDP 443 to it. - Save the three files in one folder:
docker-compose.ymland.envside by side, the Caddyfile at./caddy/Caddyfile. Replaceexample.orgwith your domain in the Caddyfile, the compose file and the .env, or let the builder do it. - Nothing in
.envneeds filling in;chmod 600 .envall the same. - Start it:
docker compose up -d docker compose logs -f caddy # watch the certificate arrive
- Open the new address (
recipes.plus your domain) in a browser and follow the notes above.
With PostgreSQL
- At your DNS provider, add an A record named
recipeson your domain pointing at the server's public IP address, and forward TCP 80, TCP 443 and UDP 443 to it. - Save the three files in one folder:
docker-compose.ymland.envside by side, the Caddyfile at./caddy/Caddyfile. Replaceexample.orgwith your domain in the Caddyfile, the compose file and the .env. - Fill the blank
MEALIE_DB_PASSWORDin.env. On the server,tr -dc A-Za-z0-9 </dev/urandom | head -c 32prints 32 random letters and digits. Thenchmod 600 .env. - Start it:
docker compose up -d docker compose logs -f caddy # watch the certificate arrive
- Open the new address (
recipes.plus your domain) in a browser and follow the notes above.
Back it up
With SQLite, the default
Mealie's docs: with SQLite (as here) all data is in /app/data/, and stopping the container and backing up that folder 'is the best way to backup your data'. Mealie also makes in-app backups under Settings > Admin Settings > Backups.
Below is the BACKUP.md the builder writes next to the compose file above: which of its folders and volumes hold data, what to copy with which container stopped, and a restore check. Pick more apps in the builder and it covers them all in one file.
# BACKUP.md built at dankhost.com for: Mealie
What to copy from the docker-compose.yml built with this file, the database dump each project documents (rewritten for the service names in that file), what to copy with which container stopped, and how to check the result. Run every command in the folder that holds docker-compose.yml.
The folders are owned by the containers' users: put sudo in front of tar if it says "Permission denied". Named volumes live under /var/lib/docker/volumes, not next to the compose file, so they are copied through a throwaway ubuntu container (Docker's documented --volumes-from method). tar makes a full copy each run; for large folders an incremental tool (restic, borg, rsync) saves time and space.
Never run "docker compose down -v" on this file: it deletes the named volumes of every app in it.
## Before you start
BACKUP=/mnt/backup/selfhost # change this: a disk or machine other than this server's system disk
mkdir -p "$BACKUP"
## Every time: the three stack files
tar czf "$BACKUP/stack-files.tar.gz" docker-compose.yml .env caddy
.env holds the database passwords and secret keys the apps were set up with; keep this archive as private as the data.
## Caddy (the reverse proxy)
Caddy's docs: 'The data directory must not be treated as a cache.' It holds the TLS certificates and their private keys; without it Caddy has to ask Let's Encrypt for every certificate again.
- caddy-data (named volume, /data in caddy)
BACK UP: TLS certificates, private keys, OCSP staples.
- caddy-config (named volume, /config in caddy)
SKIP: the last active configuration, kept for 'caddy run --resume', which this setup does not use: it starts from the Caddyfile.
- ./caddy (/etc/caddy in caddy)
IN stack-files.tar.gz: the Caddyfile, copied with the stack files above.
Copy (Caddy keeps serving while you copy):
docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu tar cvf /backup/caddy-data.tar /data
Restore check:
tar tf "$BACKUP/caddy-data.tar" > /dev/null && echo OK
docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/caddy-data.tar --strip 1"
Sources:
- Caddy docs: Conventions, Data directory: https://caddyserver.com/docs/conventions#data-directory (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)
## Mealie
Mealie's docs: with SQLite (as here) all data is in /app/data/, and stopping the container and backing up that folder 'is the best way to backup your data'. Mealie also makes in-app backups under Settings > Admin Settings > Backups.
What this compose mounts:
- mealie-data (named volume, /app/data in mealie)
BACK UP: the SQLite database, recipe images and settings.
1. Stop mealie. Mealie's docs say to stop the container before copying the folder.
docker compose stop mealie
2. Copy while mealie is stopped:
docker run --rm --volumes-from mealie -v "$BACKUP":/backup ubuntu tar cvf /backup/mealie-data.tar /app/data
3. Start it again:
docker compose start mealie
Restore check:
tar tf "$BACKUP/mealie-data.tar" > /dev/null && echo OK
Put a copy back (with mealie stopped):
docker run --rm --volumes-from mealie -v "$BACKUP":/backup ubuntu bash -c "cd /app/data && tar xvf /backup/mealie-data.tar --strip 2"
Stop it, restore the volume with the command above, start it. An in-app backup is restored from the same Backups page; that restore deletes all current data and cannot be undone.
Sources:
- Mealie docs: Backups and Restores: https://docs.mealie.io/documentation/getting-started/usage/backups-and-restoring/ (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)
With PostgreSQL
Mealie's docs describe its in-app backups (Settings > Admin Settings > Backups) and, for SQLite only, stopping the container and copying /app/data. For PostgreSQL they give no file-level method, so this plan uses PostgreSQL's own pg_dump with Mealie stopped, plus a copy of mealie-data.
Below is the BACKUP.md for the PostgreSQL version of the compose file above, written by the same code as the builder's: which of its folders and volumes hold data, the dump command the project documents, rewritten for this file's service names, what to copy with which container stopped, and a restore check.
# BACKUP.md built at dankhost.com for: Mealie
What to copy from the docker-compose.yml built with this file, the database dump each project documents (rewritten for the service names in that file), what to copy with which container stopped, and how to check the result. Run every command in the folder that holds docker-compose.yml.
The folders are owned by the containers' users: put sudo in front of tar if it says "Permission denied". Named volumes live under /var/lib/docker/volumes, not next to the compose file, so they are copied through a throwaway ubuntu container (Docker's documented --volumes-from method). tar makes a full copy each run; for large folders an incremental tool (restic, borg, rsync) saves time and space.
Never run "docker compose down -v" on this file: it deletes the named volumes of every app in it.
## Before you start
BACKUP=/mnt/backup/selfhost # change this: a disk or machine other than this server's system disk
mkdir -p "$BACKUP"
## Every time: the three stack files
tar czf "$BACKUP/stack-files.tar.gz" docker-compose.yml .env caddy
.env holds the database passwords and secret keys the apps were set up with; keep this archive as private as the data.
## Caddy (the reverse proxy)
Caddy's docs: 'The data directory must not be treated as a cache.' It holds the TLS certificates and their private keys; without it Caddy has to ask Let's Encrypt for every certificate again.
- caddy-data (named volume, /data in caddy)
BACK UP: TLS certificates, private keys, OCSP staples.
- caddy-config (named volume, /config in caddy)
SKIP: the last active configuration, kept for 'caddy run --resume', which this setup does not use: it starts from the Caddyfile.
- ./caddy (/etc/caddy in caddy)
IN stack-files.tar.gz: the Caddyfile, copied with the stack files above.
Copy (Caddy keeps serving while you copy):
docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu tar cvf /backup/caddy-data.tar /data
Restore check:
tar tf "$BACKUP/caddy-data.tar" > /dev/null && echo OK
docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/caddy-data.tar --strip 1"
Sources:
- Caddy docs: Conventions, Data directory: https://caddyserver.com/docs/conventions#data-directory (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)
## Mealie
Mealie's docs describe its in-app backups (Settings > Admin Settings > Backups) and, for SQLite only, stopping the container and copying /app/data. For PostgreSQL they give no file-level method, so this plan uses PostgreSQL's own pg_dump with Mealie stopped, plus a copy of mealie-data.
What this compose mounts:
- mealie-data (named volume, /app/data in mealie)
BACK UP: recipe images, Mealie's in-app backup files and other files; with PostgreSQL the database is not in it.
- mealie-pgdata (named volume, /var/lib/postgresql/data in mealie-postgres)
COVERED BY THE COMMAND BELOW: PostgreSQL's data files; the pg_dump below is the copy to keep.
1. Stop mealie. With Mealie stopped nothing changes between the dump and the copy of mealie-data, so recipes and their images match. The database keeps running for the dump.
docker compose stop mealie
2. Database dump for mealie-postgres:
docker compose exec -T mealie-postgres pg_dump -U mealie mealie > "$BACKUP/mealie-db.sql"
pg_dump runs inside the database container as mealie, the user the compose file creates, and writes the mealie database as SQL.
3. Copy while mealie is stopped:
docker run --rm --volumes-from mealie -v "$BACKUP":/backup ubuntu tar cvf /backup/mealie-data.tar /app/data
4. Start it again:
docker compose start mealie
Restore check:
grep -c 'PostgreSQL database dump complete' "$BACKUP/mealie-db.sql" # 1 means pg_dump finished
tar tf "$BACKUP/mealie-data.tar" > /dev/null && echo OK
Put a copy back (with mealie stopped):
docker run --rm --volumes-from mealie -v "$BACKUP":/backup ubuntu bash -c "cd /app/data && tar xvf /backup/mealie-data.tar --strip 2"
The dump goes into an empty database: on a new server, or after removing the mealie-pgdata volume, start only the database (on first start it creates an empty mealie database), load the dump, and start the rest:
docker compose up -d mealie-postgres
until docker compose exec -T mealie-postgres pg_isready -h 127.0.0.1 -U mealie; do sleep 2; done # waits until the first-start setup is over
docker compose exec -T mealie-postgres psql -U mealie -d mealie --set ON_ERROR_STOP=on < "$BACKUP/mealie-db.sql"
docker compose up -d
An in-app backup is restored from the same Backups page; that restore deletes all current data and cannot be undone.
Sources:
- Mealie docs: Backups and Restores (Postgres note): https://docs.mealie.io/documentation/getting-started/usage/backups-and-restoring/ (checked 2026-09-30)
- PostgreSQL docs: pg_dump: https://www.postgresql.org/docs/current/app-pgdump.html (checked 2026-09-30)
- Docker Official Image postgres: POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB, PGDATA (changed in 18): https://hub.docker.com/_/postgres (checked 2026-09-30)
Update it
With SQLite, the default
What docker compose pull does depends only on how each image line in the compose file above is tagged. For Mealie as this page writes it:
| Service | Image | How it is pinned | What docker compose pull does |
|---|---|---|---|
caddy | caddy:2 | Major version only (tag 2) | Takes the newest image tagged 2: minor and patch releases of 2, never 3. A new major version needs a tag edit. |
mealie | ghcr.io/mealie-recipes/mealie:v3.27.0 | Exact version (tag v3.27.0) | Does not move: stays on 3.27.0 until you edit the tag (a publisher may re-push the same version on a rebuilt base). |
What Mealie's docs say about updating
Mealie's install docs advise against the latest tag: pin a specific vX.Y.Z and update consciously, when you have time to read the release notes and do any manual steps they list.
- This file follows that advice with v3.27.0, so docker compose pull changes nothing until you edit the tag to the newer version.
The steps
- Back up first, as in Back it up above. An update can migrate Mealie's data on its first start; the copy is the way back.
mealieis pinned to an exact version (see the table), so a pull alone changes nothing there: to update Mealie, first edit its tag indocker-compose.ymlto the version you want.- Download the new images. Running containers are not touched yet:
docker compose pull
- Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:
docker compose up -d
- Watch Mealie start (Ctrl+C stops following the log, not the app):
docker compose logs -f mealie
- Optional: remove the old images the pull left without a tag. This covers every stack on the machine, not only this one:
docker image prune
With PostgreSQL
What docker compose pull does depends only on how each image line in the compose file above is tagged. For Mealie as this page writes it:
| Service | Image | How it is pinned | What docker compose pull does |
|---|---|---|---|
caddy | caddy:2 | Major version only (tag 2) | Takes the newest image tagged 2: minor and patch releases of 2, never 3. A new major version needs a tag edit. |
mealie | ghcr.io/mealie-recipes/mealie:v3.27.0 | Exact version (tag v3.27.0) | Does not move: stays on 3.27.0 until you edit the tag (a publisher may re-push the same version on a rebuilt base). |
mealie-postgres database | postgres:17 | Major version only (tag 17) | Takes the newest image tagged 17: minor and patch releases of 17, never 18. A new major version needs a tag edit. |
Do not raise the major version of mealie-postgres by editing its tag. Keep its tag, 17, as it is when you update Mealie.
PostgreSQL's docs: a new major version may change how data is stored on disk, so a data folder written by an older major version will not start under a newer one (the server refuses it). Moving needs a dump and restore (pg_dumpall, then load the dump into the new version) or pg_upgrade. Minor releases of the same major version never change the storage format. Source: PostgreSQL docs: Upgrading a PostgreSQL Cluster checked 2026-09-30
What Mealie's docs say about updating
Mealie's install docs advise against the latest tag: pin a specific vX.Y.Z and update consciously, when you have time to read the release notes and do any manual steps they list.
- This file follows that advice with v3.27.0, so docker compose pull changes nothing until you edit the tag to the newer version.
- Mealie and PostgreSQL are updated separately, one tag at a time. The postgres tag, 17, takes every 17.x release on docker compose pull; PostgreSQL says minor releases never change the storage format, so that is safe.
- Mealie's PostgreSQL page warns that upgrading PostgreSQL to a new major version needs manual steps: the new version cannot open the old data, and PostgreSQL's Upgrading a PostgreSQL Cluster page says to dump the data and restore it into the new version (or use pg_upgrade). With this file: stop Mealie, dump, check the dump, remove only the database container and its volume, edit the tag, start the database alone, load the dump, start the rest:
docker compose stop mealie docker compose exec -T mealie-postgres pg_dump -U mealie mealie > mealie-pg17.sql grep -c 'PostgreSQL database dump complete' mealie-pg17.sql # must print 1 before you go on docker compose rm -sf mealie-postgres docker volume ls --filter name=mealie-pgdata # its full name starts with your project name; then: docker volume rm <that name> docker compose up -d mealie-postgres # after editing the tag until docker compose exec -T mealie-postgres pg_isready -h 127.0.0.1 -U mealie; do sleep 2; done # waits until the first-start setup is over docker compose exec -T mealie-postgres psql -U mealie -d mealie --set ON_ERROR_STOP=on < mealie-pg17.sql docker compose up -d
The steps
- Back up first, as in Back it up above. An update can migrate Mealie's data on its first start and its database with it; the copy is the way back.
mealieis pinned to an exact version (see the table), so a pull alone changes nothing there: to update Mealie, first edit its tag indocker-compose.ymlto the version you want.- Download the new images. Running containers are not touched yet:
docker compose pull
- Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:
docker compose up -d
- Watch Mealie start (Ctrl+C stops following the log, not the app):
docker compose logs -f mealie
- Optional: remove the old images the pull left without a tag. This covers every stack on the machine, not only this one:
docker image prune
Locked out? Reset the admin password
Sets a new password for a Mealie user with the script its FAQ gives for anyone locked out. If you log in through external auth, the script also offers to switch you back to local login.
Run the script in the container. The path names the Python version inside the image: 3.12 in the FAQ for v3.27.0, the tag this file pins (newer FAQs show 3.14 for newer images). Source: Mealie FAQ at v3.27.0: How can I change my password? read 2026-10-03
docker compose exec mealie python /opt/mealie/lib64/python3.12/site-packages/mealie/scripts/change_password.py
Sources
Every page below was fetched on the date shown.
- Mealie README (About The Project) checked 2026-09-23 (what it does)
- Mealie docs: Installation, SQLite (Recommended) checked 2026-09-23 (hardware requirements, update notes, PostgreSQL version, PostgreSQL update notes)
- Mealie docs: Installation Checklist (Docker, 32bit Support) checked 2026-09-23 (hardware requirements, PostgreSQL version)
- Mealie docs: Installation, SQLite (Recommended) docker-compose.yaml checked 2026-09-23 (compose definition and proxy settings)
- Mealie docs: Installation Checklist (default credentials, architectures) checked 2026-09-23 (compose definition and proxy settings)
- Caddy docs: Keep Caddy running (Docker Compose section) checked 2026-09-23 (Caddy)
- Vaultwarden wiki: Caddy with HTTP challenge (uses the caddy:2 image) checked 2026-09-23 (Caddy)
- Mealie docs: Backups and Restores checked 2026-09-24 (backup plan, PostgreSQL backup plan)
- Docker docs: Volumes, Back up, restore, or migrate data volumes checked 2026-09-24 (backup plan)
- Caddy docs: Conventions, Data directory checked 2026-09-24 (backup plan)
- Docker docs: docker compose pull checked 2026-09-30 (update steps)
- Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30 (update steps)
- Docker docs: docker image prune checked 2026-09-30 (update steps)
- Mealie docs: Installation, PostgreSQL docker-compose.yaml checked 2026-09-30 (PostgreSQL version, PostgreSQL update notes)
- Docker Official Image postgres: POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB, PGDATA (changed in 18) checked 2026-09-30 (PostgreSQL version, PostgreSQL backup plan)
- PostgreSQL docs: pg_dump checked 2026-09-30 (PostgreSQL backup plan)
- PostgreSQL docs: Upgrading a PostgreSQL Cluster checked 2026-09-30 (PostgreSQL update notes, database upgrade)