You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed Mealie with Postgres for SQL using Portainer on my Synology DS923+ a few months ago and it has been working great.
I accidentally upgraded the mealie and mealie-db through the Container Manager in DSM instead of Portainer and now the mealie-db container starts and immediately stops with exit code 127.
the log for the mealie-db shows this:
PostgreSQL Database directory appears to contain a database; Skipping initialization
/usr/local/bin/docker-entrypoint.sh: line 351: exec: postgres: not found
I am not sure what to do here as I am Linuxly and Dockerly challenged. Should I just make a new container for mealie and do proper backups moving forward? I can console into the mealie container as it is running fine but not mealie-db. I have less than 50 recipes entered so not the end of the world but if there's anyway to get this running without starting from scratch, I would be very grateful.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I installed Mealie with Postgres for SQL using Portainer on my Synology DS923+ a few months ago and it has been working great.
I accidentally upgraded the mealie and mealie-db through the Container Manager in DSM instead of Portainer and now the mealie-db container starts and immediately stops with exit code 127.
the log for the mealie-db shows this:
PostgreSQL Database directory appears to contain a database; Skipping initialization
/usr/local/bin/docker-entrypoint.sh: line 351: exec: postgres: not found
The compose file used in Portainer:
`version: "3.9"
services:
db:
image: postgres
container_name: Mealie-DB
hostname: mealie-db
mem_limit: 1g
cpu_shares: 768
security_opt:
- no-new-privileges:true
healthcheck:
test: ["CMD", "pg_isready", "-q", "-d", "mealie", "-U", "mealieuser"]
timeout: 45s
interval: 10s
retries: 10
volumes:
- /volume1/docker/mealie/db:/var/lib/postgresql/data:rw
environment:
POSTGRES_DB: mealie
POSTGRES_USER: mealieuser
POSTGRES_PASSWORD: mealiepass
restart: on-failure:5
mealie:
image: ghcr.io/mealie-recipes/mealie:nightly
container_name: Mealie
hostname: mealie
mem_limit: 3g
cpu_shares: 768
security_opt:
- no-new-privileges:true
read_only: true
ports:
- 9925:9000
volumes:
- /volume1/docker/mealie/data:/app/data/:rw
environment:
TZ: America/Toronto
PUID: 1026
PGID: 100
MAX_WORKERS: 1
WEB_CONCURRENCY: 1
ALLOW_SIGNUP: true #or false
BASE_URL: http://192.168.99.25 #or https://mealie.yourname.synology.me
DB_ENGINE: postgres
POSTGRES_USER: mealieuser
POSTGRES_PASSWORD: mealiepass
POSTGRES_SERVER: mealie-db
POSTGRES_PORT: 5432
POSTGRES_DB: mealie
SMTP_HOST:
SMTP_PORT: 587
SMTP_FROM_NAME: Mealie
SMTP_AUTH_STRATEGY: TLS # Options: 'TLS', 'SSL', 'NONE'`
I am not sure what to do here as I am Linuxly and Dockerly challenged. Should I just make a new container for mealie and do proper backups moving forward? I can console into the mealie container as it is running fine but not mealie-db. I have less than 50 recipes entered so not the end of the world but if there's anyway to get this running without starting from scratch, I would be very grateful.
Beta Was this translation helpful? Give feedback.
All reactions