docker network create on wslc
docker network create is partial on wslc 2.9.4.0. The command exists as wslc network create, but its flags, defaults or output format do not match Docker byte-for-byte, so the shape of your invocation decides whether it needs an edit.
| Docker command | docker network create |
|---|---|
| Status on wslc 2.9.4.0 | Partial |
| wslc command | wslc network create |
| Verified against | wslc 2.9.4.0, windows-2025 runner |
Measured detail. Has -d/--driver (default bridge), --subnet, --gateway, --internal, -o/--opt, -l. On wslc run, --network none works but --network host is rejected: "host mode networking is not supported".
The wslc equivalent
# Docker
docker network create
# wslc
wslc network createwslc network create [<options>] <network-name>
Straight from wslc network create --help on wslc 2.9.4.0 .
| Argument | Meaning |
|---|---|
network-name | Network name |
| Flag | Meaning |
|---|---|
-d,--driver | Specify network driver name (default: bridge) |
-o,--opt | Set driver specific options |
-l,--label | Network metadata setting |
--gateway | IPv4 or IPv6 gateway for the subnet |
--internal | Restrict external access to the network |
--subnet | Subnet in CIDR format that represents a network segment |
How we know
Confirmed by reading wslc --help output and, where the behaviour depends on execution rather than argument parsing, by running the command against wslc 2.9.4.0 on a Windows Server 2025 GitHub Actions runner. Unrecognized flags and subcommands fail loudly on wslc -- the parser answers Argument name was not recognized for the current command and exits non-zero -- so a typo is unlikely to be misread as support. The risk runs the other way: a Docker habit that happens to parse (like wslc ps still working) can mask a difference in what the flags underneath it do.
Claims on this site are re-checked by a scheduled workflow that runs the commands again on
a fresh Windows Server 2025 runner and fails when a documented behaviour stops matching
reality. wslc ships roughly every two weeks during the preview, so treat any page that
disagrees with your own machine as the page being stale, and check the version you are on
with wslc version.
Where this fits
This is one row of the full Docker to wslc cheat sheet,
which covers every command and every flag on a single page. If the workload you are
porting uses Docker Compose rather than bare docker invocations, start from
Compose key support instead -- docker network create rarely appears verbatim in a compose.yaml, and the key-level page maps YAML fields
directly to the flags shown above. For a whole script at once, paste it into the
command converter and get every line classified in the same pass.