Repository navigation
fix(environment): restart serving containers after a docker restart - #60
Merged
Merged
Conversation
Without a restart policy, ignis, db and the https proxy stayed down after a Docker daemon restart or host reboot until compose was run again. Set restart: unless-stopped on every long-running service in all five compose files, development and production alike. build-db keeps no policy: it is a one-shot seed job, and unless-stopped would rerun it every time the daemon starts. Closes #59
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
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.
Summary
Adds
restart: unless-stoppedtodb,ignisandproxyin every compose file underenvironment/, so the serving containers come back after a Docker daemon restart or host reboot.build-dbis a one-shot seed job and keeps no policy.Deployment note
The policy lives in the compose file, not the image, so changing
IGNIS_IMAGE_TAGalone does not apply it. An existing deployment picks it up by taking the updated compose file and runningdocker compose up -d, or applies it to running containers withdocker update --restart unless-stopped <container>.Verification
docker compose -f <file> configon each of the five files showsrestart: unless-stoppedon the serving services and no restart policy onbuild-db.Closes #59