Add restart policy for Caddy (eg start Caddy when docker daemon boots/restarts)#36
Open
davidjb wants to merge 1 commit intocabotapp:masterfrom
Open
Add restart policy for Caddy (eg start Caddy when docker daemon boots/restarts)#36davidjb wants to merge 1 commit intocabotapp:masterfrom
davidjb wants to merge 1 commit intocabotapp:masterfrom
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.