This repository was archived by the owner on Oct 31, 2024. It is now read-only.
dwe-controls should not have restart=always#16
Open
ethanbowering24 wants to merge 1 commit intoDeepWaterExploration:mainfrom
Open
dwe-controls should not have restart=always#16ethanbowering24 wants to merge 1 commit intoDeepWaterExploration:mainfrom
ethanbowering24 wants to merge 1 commit intoDeepWaterExploration:mainfrom
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
A simple systemd service with
Restart=alwayswill always restart the service even if it is successful, implying it should not terminate.docker startsimply runs a container and terminates. When restart=always is used with this, it will just try to start it again for no reason, and systemd will say that the service has failed (failed (Result: start-limit-hit)), even though the docker container is running fine.If
Restart=on-failureis used instead, then systemd will say that it is inactive, which is more accurate since docker start has terminated successfully. Or a oneshot service could be used withRemainAfterExit=trueso systemd reports it as active but exited, since the container is still running.