Add --restart unless-stopped to container#343
Open
woltspace-jerpint[bot] wants to merge 1 commit into
Open
Conversation
Auto-restarts the container on host reboot or docker daemon restart, but respects manual `woltspace stop`. No more "have to start the container every time." Same flag added to backup-restore command examples and HUMANS.md docs for consistency. No sudo needed — host user just needs to be in the docker group (standard linux setup, automatic on macOS Docker Desktop). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
woltspace stopWhy
Today
woltspace startrunsdocker run -d ...with no restart policy, so a host reboot leaves the container down until the user manually re-runswoltspace start.--restart unless-stoppedis the canonical fix:docker stop/woltspace stopThis matches the behavior described in the original chat ("not always — exception is if you stop it manually").
No sudo
The flag is just a
docker runargument, so it inherits whatever permissions the user already has fordocker. On macOS Docker Desktop sudo is never needed; on Linux the user just needs to be in thedockergroup (sudo usermod -aG docker $USER), which is the normal setup. No sudo invocation introduced.Existing containers
This only affects new containers created via
woltspace start. To upgrade an already-running container without recreating it:Test plan
woltspace starton linux host →docker inspect woltspace --format '{{.HostConfig.RestartPolicy.Name}}'returnsunless-stoppedwoltspace stop→ reboot → container stays stopped