You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e6960f7
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/backends/wslc/wsl-container-getting-started.md
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -415,6 +415,13 @@ TCP only — the WSLC SDK runtime returns `E_NOTIMPL` for UDP, so a `"udp"`
415
415
protocol is rejected. Two entries claiming the same `windowsPort` are also
416
416
rejected.
417
417
418
+
With the [built-in proxy](#built-in-proxy), including a policy that denies
419
+
everything else, the mapping is set on the proxy container, which relays it to
420
+
the workload's `containerPort`. Each mapping is reachable only on Windows
421
+
`127.0.0.1`, regardless of `network.ingress`, and the workload sees the proxy
422
+
container's address as the source. Each mapping accepts at most 512 open
423
+
connections; more wait until one closes.
424
+
418
425
The separate `provision` operation takes the same list under
419
426
`wslc.provision.portMappings`, which requires schema `1.1.0-alpha`:
420
427
@@ -517,7 +524,7 @@ no separate `--setup-wslc` step is required.
517
524
| Type | Exact policy | WSLC behavior |
518
525
|---|---|---|
519
526
| Bridged | Egress, ingress, and host-loopback defaults all `allow`, without egress rules | The container gets an address on WSLC's NAT network in the session VM. It can reach the internet, the local network, and [port mappings](#port-mappings) forward Windows ports into it. Windows host loopback isn't accessible. Nothing is filtered. |
520
-
| Isolated | All three defaults omitted or `deny`, without egress allow rules | No networking. The container only has its own loopback interface. It can't reach anything outside itself, and nothing can reach it. |
527
+
| Isolated | All three defaults omitted or `deny`, without egress allow rules or port mappings | No networking. The container only has its own loopback interface. It can't reach anything outside itself, and nothing can reach it. |
521
528
| Built-in proxy | Any other combination, create-and-run execution | Egress filtered by the [built-in proxy](#built-in-proxy)|
522
529
| Built-in proxy | Any other combination, container lifecycle operations | Rejected |
523
530
@@ -576,13 +583,14 @@ as follows:
576
583
- Rejected with the proxy: `allow` entries for any protocol except `tcp`
577
584
(including entries without `ports`, which cover every protocol; use
578
585
`"ports": [{ "protocol": "tcp" }]` for every TCP port), IPv6
0 commit comments