fix: enable automatic container restart on failure or system reboot#112
Merged
guyb1 merged 1 commit intoonecli:mainfrom Mar 26, 2026
Merged
fix: enable automatic container restart on failure or system reboot#112guyb1 merged 1 commit intoonecli:mainfrom
guyb1 merged 1 commit intoonecli:mainfrom
Conversation
**Current behavior:** - Docker containers do not restart if the daemon restarts or the machine reboots - Service downtime until manual intervention **New behavior:** - Added 'restart: unless-stopped' policy to postgres and app services - Containers automatically recover from crashes - Containers restart after Docker daemon or system reboots - Exception: containers stopped explicitly via 'docker stop' or 'docker-compose down' stay stopped This aligns with production best practices for service resilience and high availability.
guyb1
force-pushed
the
feat/docker-restart-policy
branch
from
4ac7ebf to
18bcbb6
Compare
guyb1
changed the title
Contributor
|
Thanks for this! Merging now. @evenisse |
hisgarden
pushed a commit
to hisgarden/onecli
that referenced
this pull request
Mar 27, 2026
…necli#112) **Current behavior:** - Docker containers do not restart if the daemon restarts or the machine reboots - Service downtime until manual intervention **New behavior:** - Added 'restart: unless-stopped' policy to postgres and app services - Containers automatically recover from crashes - Containers restart after Docker daemon or system reboots - Exception: containers stopped explicitly via 'docker stop' or 'docker-compose down' stay stopped This aligns with production best practices for service resilience and high availability.
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
2 participants
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.
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
Feature - Infrastructure/DevOps improvement
What is the current behavior?
Docker containers do not automatically restart if the Docker daemon restarts or the host machine reboots. This results in service downtime until manual intervention is required to bring containers back online.
What is the new behavior?
Added the
restart: unless-stoppedpolicy to both thepostgresandappservices in the docker-compose configuration.Benefits:
docker stopordocker-compose downremain stopped, allowing for controlled maintenanceAdditional context
This change aligns with production best practices for containerized services and follows Docker documentation recommendations for service resilience.
Changes made:
docker/docker-compose.ymlto addrestart: unless-stoppedto postgres servicedocker/docker-compose.ymlto addrestart: unless-stoppedto app service