Skip to content

Serving containers stay down after a Docker restart #59

Closed

Description

@jravani

None of the compose files under environment/ sets a restart policy. After a Docker daemon restart or a host reboot, ignis, db and (https only) proxy stay down until someone runs docker compose up again.

Add restart: unless-stopped to every long-running service in all five compose files:

  • environment/http/docker-compose.yml, docker-compose.prod.yml: db, ignis
  • environment/https/docker-compose.yml, docker-compose.prod.yml, docker-compose.quickstart.yml: db, ignis, proxy

build-db is a one-shot seed job and keeps no restart policy.

The policy is part of the compose file, not the image, so a deployment picks it up by using the updated compose file; changing IGNIS_IMAGE_TAG alone does not apply it.

Activity

  1. added a commit that references this issue on Oct 13, 2026
    84e6c13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions