[BUG] `latest-nonroot` container crashes with exit code 159 on ARM64 (Raspberry Pi)

[TheBlackDragon4]

Hi Almar,

first of all, thank you for building TimeTagger – it's an elegant and minimalist time tracker that I really want to self-host.

Unfortunately, I’ve followed the self-hosting guide (https://timetagger.app/articles/selfhost2/) exactly, but the container ghcr.io/almarklein/timetagger:latest-nonroot crashes instantly with exit code 159 when running on Raspberry Pi OS 64-bit (ARM64).

---

My setup

• OS: Raspberry Pi OS 64-bit (Debian-based)
• Hardware: Raspberry Pi 4
• Docker installed via get.docker.com
• Docker Compose version 2 plugin
• Architecture: aarch64
• Docker reports: Architecture: aarch64

---

What I tried

• docker compose up -d using your provided docker-compose.yml
• platform: linux/arm64 explicitly set
• tested with and without TIMETAGGER_CREDENTIALS
• verified the volume is mounted correctly
• tried minimal docker run (without volumes or env)
• logs remain empty (docker logs = no output)
• container restarts constantly: Restarting (159)
• docker exec is not possible due to rapid restart
• docker inspect shows no IP assigned
• docker manifest inspect confirms arm64 support

---

Observations

• Exit code 159 typically indicates a Bash or Python execution crash
• TimeTagger never even starts the HTTP listener
• Volume and ports seem irrelevant – even a minimal container crashes
• This seems to happen before any log output is possible

---

What I’m hoping for

• Could you verify if the latest-nonroot image works on an actual ARM64 system?
• Or clarify if TimeTagger is currently not tested on ARM64 despite manifest support?
• If possible, provide a minimal log or debugging strategy?

Thanks in advance, and again: the app looks amazing – would love to get it working on my Raspberry Pi!

[almarklein]

I don't think the provided Docker image can run on ARM64. Best would be to create your own Docker image using an OS that runs on it. A bit like this but with a different base OS.