Repository navigation
docs(container): say that WSL shuts an idle distro down, and how to stop it - #103
Merged
Merged
Conversation
…top it docs/container-browser.md said WSL starts when something on Windows starts it. It did not say that WSL then shuts an idle distro down 15 s after its last wsl.exe ends (`instanceIdleTimeout`), docker and the browser container with it. Found 2026-11-10 from the WSL host's logs: the Windows System log, pm2's log, systemd and Docker. After the 2026-10-28 restart a logon shortcut running `wsl.exe ... -- true` started the distro twice. It shut down 18 s later each time, and the container stayed down until a terminal was opened 11 minutes after logon. The doc now gives `[general] instanceIdleTimeout=-1` for %UserProfile%\.wslconfig, per Microsoft's wsl-config page. The setting was added to that host's .wslconfig the same day. It takes effect when WSL next starts, and has not been observed across a restart yet. Claude-Session: https://claude.ai/code/session_01EMqNwnnhHXznd2P2PDsaDV
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
What this touches
2 file(s), 25 line(s) changed. Tests unchanged. This is an automated first pass, not a review. CI is the gate; a person decides. |
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.
What changed
The WSL bullet under "Keep the Docker engine running" in
docs/container-browser.mdonly said that WSL starts when something on Windows starts it. It left out the part that kept the browser container down after a Windows restart: WSL shuts an idle distro down 15 s after its lastwsl.exeends (instanceIdleTimeout, default 15000 ms per Microsoft's wsl-config page). Docker and the container stop with it.The bullet now gives the setting that turns this off,
[general] instanceIdleTimeout=-1in%UserProfile%\.wslconfig, and says it takes effect the next time WSL starts. There is also a CHANGELOG line.Evidence (WSL host, read from logs on 2026-11-10, no restart made)
Sources: the Windows System log, pm2's log, systemd and Docker. Times are KST, 2026-10-28.
wsl.exe -d Ubuntu -u ... -- trueWhenever the distro did start, docker and the
unless-stoppedcontainers came back within about 3 s.Not verified
.wslconfigon 2026-11-10. It has not yet been observed across a Windows restart.