docker logs on wslc
docker logs is identical on wslc 2.9.4.0: the command is wslc logs, same verb, same binary swap. That does not mean every flag or default carries over unchanged, though -- see the measured difference below before assuming a script ports without edits.
| Docker command | docker logs |
|---|---|
| Status on wslc 2.9.4.0 | Identical |
| wslc command | wslc logs |
| Verified against | wslc 2.9.4.0, windows-2025 runner |
Measured detail. Has -f/--follow, -n/--tail, -t/--timestamps, --since, --until. Note the short form is -n, not Docker’s unabbreviated --tail only.
The wslc equivalent
# Docker
docker logs
# wslc
wslc logswslc logs [<options>] <container-id>
Straight from wslc logs --help on wslc 2.9.4.0 .
| Argument | Meaning |
|---|---|
container-id | Container ID |
| Flag | Meaning |
|---|---|
-f,--follow | Follow log output |
-n,--tail | Number of lines to show from the end of the logs |
-t,--timestamps | Show timestamps in log output |
--since | Show logs since timestamp (Unix epoch seconds or RFC3339, e.g. 2024-01-15T10:30:00Z) |
--until | Show logs before timestamp (Unix epoch seconds or RFC3339, e.g. 2024-01-15T10:30:00Z) |
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 logs 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.