Do I have to rewrite docker rm scripts to use wslc undefined?

Depends on whether the short form is still accepted on the build you are running. wslc remove works too, with aliases rm and delete. -f forces removal of a running container. Treat the short form as convenient, not guaranteed, and prefer the noun-then-verb form in anything you plan to keep working past this preview.

What happens if I run docker rm unmodified against wslc?

A well-formed converter rewrites the binary name and, where needed, the flags -- see the wslc command above. Running the literal Docker string against wslc directly does not work; wslc has its own argument parser and does not alias Docker's exact syntax beyond the specific renames this site documents.

docker rm on wslc

Q: What is the wslc equivalent of docker rm?

wslc undefined. wslc remove works too, with aliases rm and delete. -f forces removal of a running container.

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

docker rm is renamed on wslc 2.9.4.0: it moved to wslc undefined under wslc's noun-then-verb naming. wslc rm 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 command	`docker rm`
Status on wslc 2.9.4.0	Renamed
wslc command	`wslc container remove`
Verified against	wslc 2.9.4.0, windows-2025 runner

Measured detail. wslc remove works too, with aliases rm and delete. -f forces removal of a running container.

The wslc equivalent

# Docker
docker rm

# wslc
wslc undefined

`wslc remove [<options>] <container-id>`

Straight from wslc rm --help on wslc 2.9.4.0 — also invocable as delete, rm.

Argument	Meaning
`container-id`	Container ID

Flag	Meaning
`-f,--force`	Delete containers even if they are running

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

docker rm on wslc

The wslc equivalent

`wslc remove [<options>] <container-id>`

How we know

Where this fits

Related guides

docker cp →

docker images →

docker ps →