Mealie starts, stops and restart in loop

[nocrack21]

Hi folks,

Just tried installing mealie on an RPI4. I am not managing to run mealie properly using docker compose and your instructions.
After starting it, running docker compose top I get this error
Error response from daemon: Container 65b7abf855d953a8de9cdcbe35cfd237645b561eee4cb741fc4ad90853cd2699 is restarting, wait until the container is running
Docker log mealie or docker compose log mealie are blank so I am not sure where else I can provide log from

yaml file is box standard using your sqlite version and only adding the plarform tag othewise docker was throwing an error trying to pull the wrong code base

services:
  mealie:
    image: ghcr.io/mealie-recipes/mealie:latest
    platform: linux/arm64
    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: true
      PUID: 1000
      PGID: 1000
      TZ: Australia/Sydney
      MAX_WORKERS: 1
      WEB_CONCURRENCY: 1
      BASE_URL: https://192.168.1.3

volumes:
  mealie-data:

Running docker 27.0.3 and a homeassistant container fine
kernel Linux 6.1.21-v8+ aarch64
Distro Raspbian GNU/Linux 11 (bullseye)

Thanks for your help!

[boc-the-git]

docker compose logs is the command you want; what does that get?

[nocrack21]

Sorry forgot the s when I wrote my message. So as per above, it returns nothing at all

[boc-the-git]

Do you have any important data in Mealie? I'm assuming not.

Run docker compose down -v && docker ps && docker compose top && cat docker-compose.yml && docker compose up -d && docker compose logs && docker compose top
And share the whole output here. Feel free to redact some of docker ps if you need to.

Ideally you'd split those commands out and run them sequentially - I get the impression you know how to do that. It'd give us more meaningful output to see it run that way with contextual output.

[nocrack21]

Thanks for your help. See requested info below

No important data in Mealie

docker compose down -v
[+] Running 1/0
✔ Volume mealie_mealie-data Removed 0.0s

docker ps
ghcr.io/sabeechen/hassio-google-drive-backup-armv7:0.112. 0.0.0.0:1627->1627/tcp, :::1627->1627/tcp, 8099/tcp
ghcr.io/home-assistant/armv7-hassio-multicast:2024.03.0
ghcr.io/home-assistant/armv7-hassio-audio:2023.12.0
ghcr.io/home-assistant/armv7-hassio-dns:2024.04.0
ghcr.io/home-assistant/armv7-hassio-cli:2024.05.0
homeassistant/armv7-hassio-supervisor
ghcr.io/home-assistant/raspberrypi4-homeassistant:2024.6.3
ghcr.io/home-assistant/armv7-hassio-observer:2023.06.0 0.0.0.0:4357->80/tcp, :::4357->80/tcp

docker compose top
Empty

cat docker-compose.yml
services:
mealie:
image: ghcr.io/mealie-recipes/mealie:latest
platform: linux/arm64
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: true
PUID: 1000
PGID: 1000
TZ: Australia/Sydney
MAX_WORKERS: 1
WEB_CONCURRENCY: 1
BASE_URL: https://192.168.1.3

volumes:
mealie-data:

docker compose up -d
[+] Running 4/4
✔ Network mealie_default Create... 0.2s
✔ Volume "mealie_mealie-data" C... 0.0s
✔ Container mealie Started 1.3s
! mealie Your kernel does not support memory limit capabilities or the cgroup is not mounted. Limitation discarded. 0.0s

docker compose logs
Empty

docker compose top
Error response from daemon: Container bf8baa5d2c521054d6f0d3e9bee78a64d0ce715241792bdcdbdc5697ed506a95 is restarting, wait until the container is running

Cheers

[boc-the-git]

Can you try removing the deploy config and see if that changes anything?

[nocrack21]

No changes unfortunately

…

On Thu, 25 July 2024, 7:15 am boc-the-git, ***@***.***> wrote: Can you try removing the deploy config and see if that changes anything? — Reply to this email directly, view it on GitHub <#3934 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVTI6WP2ARN36UPN2WRG4CLZOAKODAVCNFSM6AAAAABLLJGLESVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJUGI2DOMI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[boc-the-git]

My best guess at this point is something's not quite right with either the ARM image in general, or at least the version you've pulled. I don't know how many people actually use the ARM image..

I find it slightly odd you need to specify the platform in docker-compose.. in my previous experience using a pi I don't recall needing to do that, docker was always capable of pulling the correct image for the platform. No idea if that's a relevant factor 🤔

[CallumMcMahon]

Posting here in case others have the same problem I did. Wasn't specific to Mealie in the end but was the first app I self-hosted and docker provided no logs as to why the process kept restarting in a loop.
Turns out I was trying to run the container rootless, and missed the command sudo loginctl enable-linger $(whoami) which meant that systemd was cleaning up the service at logout. Hopefully this helps someone