docker stats on wslc
docker stats is partial on wslc 2.9.4.0. The command exists as wslc stats, 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 stats |
|---|---|
| Status on wslc 2.9.4.0 | Partial |
| wslc command | wslc stats |
| Verified against | wslc 2.9.4.0, windows-2025 runner |
Measured detail. Prints a one-shot snapshot, not a live stream: there is no --no-stream because it never streams. Has -a, --format json|table, --no-trunc.
The wslc equivalent
# Docker
docker stats
# wslc
wslc statswslc stats [<options>] [<container-id>]
Straight from wslc stats --help on wslc 2.9.4.0 .
| Argument | Meaning |
|---|---|
container-id | Container ID |
| Flag | Meaning |
|---|---|
-a,--all | Show all regardless of state. |
--format | Output formatting (json or table) (Default: table) |
--no-trunc | Do not truncate output |
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 stats 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.