wslcontainers
Ask AI wslc 2.9.4.0

docker images on wslc

Updated 2026-07-27 · 3 min read · wslc public preview

docker images is renamed on wslc 2.9.4.0: it moved to wslc undefined under wslc's noun-then-verb naming. wslc images still runs too on this build -- see the note below for whether that overlap is guaranteed or just how the preview currently parses it.

Docker commanddocker images
Status on wslc 2.9.4.0Renamed
wslc commandwslc image list
Verified againstwslc 2.9.4.0, windows-2025 runner

Measured detail. wslc images also works; both forms are accepted.

The wslc equivalent

# Docker
docker images

# wslc
wslc undefined

wslc image list [<options>]

Straight from wslc images --help on wslc 2.9.4.0 — also invocable as ls.

FlagMeaning
-f,--filterFilter output based on conditions provided
--formatOutput formatting (json or table) (Default: table)
--no-truncDo not truncate output
-q,--quietOutputs the container IDs only
--verboseOutput verbose details

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 images 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.

Related guides