Skip to content

hotfix: pin docker-compose to GHCR :1.4.0 to restore production #150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MBombeck merged 1 commit into from
May 8, 2026
+10 −4
Merged

hotfix: pin docker-compose to GHCR :1.4.0 to restore production #150

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,16 @@ services:
# For horizontal scaling switch to the web/worker split below
# (HEALTHLOG_PROCESS_TYPE=web on this service + uncomment app-worker).
app:
image: ghcr.io/mbombeck/healthlog:latest
build:
context: .
dockerfile: Dockerfile
# HOTFIX: pinned to the v1.4.0 GHCR multi-arch image (linux/amd64 +
# linux/arm64) while a runtime regression introduced in the v1.4.1
# source build is investigated. The locally-built image from main
# HEAD currently produces a container that boots Next.js + the
# background workers but never accepts HTTP on :3000, so the
# Docker healthcheck fails and Traefik returns 503. v1.4.0 is the
# last release verified healthy on production. Self-hosters who
# want to build from source can re-add the `build:` block locally
# via a docker-compose.override.yml.
image: ghcr.io/mbombeck/healthlog:1.4.0
container_name: healthlog-app
ports:
- "3000:3000"
Expand Down
Loading