Skip to content

Conversation

@davidjb
Copy link

@davidjb davidjb commented Dec 4, 2019

The Caddy container currently has no restart policy, meaning that if the host/Docker daemon restarts (or Caddy errors/quits for some reason), Caddy will be left offline and thus Cabot becomes inaccessible, requiring a manual start or restart to get Caddy online. The other containers (https://github.com/cabotapp/docker-cabot/blob/master/docker-compose.yml) have restart policies of always; this PR adds the same for Caddy.

The Caddy container has no restart policy, meaning that if the host/Docker daemon restarts (or Caddy errors/quits for some reason), Caddy will be left offline and thus Cabot becomes inaccessible, requiring a manual start or restart to get Caddy online.  All the other containers (https://github.com/cabotapp/docker-cabot/blob/master/docker-compose.yml) have restart policies of `always`; this PR adds the same for Caddy, making it consistent with the rest of the application.
@JeanFred JeanFred requested a review from frankh December 4, 2019 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant