External/SnapOtter
1
0
Fork 0
mirror of https://github.com/snapotter-hq/SnapOtter.git synced 2026-08-03 07:46:42 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs(deployment): note the WSL2 Windows-host loopback gap (#689)

Browse Source 
Docker-in-WSL2 stacks can be reachable from every other device while localhost times out on the Windows host itself, even with mirrored networking. Tell Windows users what to expect and how to reach the app. Fixes #676.
This commit is contained in:
SnapOtter
2026-07-30 10:31:04 +08:00
committed by GitHub
parent 53cb9d0c70
commit 142aeaf9c5
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/guide/deployment.md
+6
View File
@@ -579,6 +579,12 @@ Fix whatever broke the first start (usually: free the port), then force the app
docker compose up -d --force-recreate SnapOtter
```
### Windows: reachable from other devices, not from the PC itself {#windows-wsl2-loopback}
With Docker running inside WSL2 (the usual Windows setup), the stack can be reachable from every other machine on your network while `http://localhost:1349` times out on the Windows host itself, even with WSL's mirrored networking mode enabled. The port never shows up in Windows `netstat`, and nothing is wrong with the containers.
Open the app from another device, or from inside the distro using its own address (`hostname -I` in the WSL shell). If localhost forwarding happens to work on your WSL version, treat it as a bonus rather than something to depend on.
## CI/CD {#ci-cd}
The GitHub repository has three workflows: