wslc error diagnostic
Paste the output you got. This names the specific wslc limitation behind it
and gives concrete steps, grounded on documented failure modes rather than generic
Docker advice.
Try an example
What it checks for
The analyser matches your output against the failure modes wslc actually has, then explains the one that fits. These are the recurring ones:
| Symptom | Underlying wslc limitation |
|---|---|
ldconfig failed with status 0x100 on --gpus all | --gpus exists, but the host has no GPU to pass through. |
Argument name was not recognized: --device | No generic device passthrough. Use --gpus for GPUs. |
Invalid memory argument value: '512m' | Memory units must be uppercase: 512M, not 512m. |
| host mode networking is not supported | --network host is refused; --network none is fine. |
| Could not find a valid Docker environment | Daemonless: no dockerd, no socket, no Engine API. |
unknown command compose | No Compose runtime. Use the migration analyser. |
unknown command restart / cp / system prune | No wslc restart; cp needs the noun form
(wslc container cp); prune per noun instead of system prune. |
Permission denied on /mnt/c/... | VirtioFS host shares are owned by the mapped user. |
exec format error | No --platform and no emulation; image must match host arch. |
Argument name was not recognized: --restart | No supervisor, so no restart policies. Use stop then start. |
| address already in use | Stale container, or the port sits in a Windows reserved range. |
Check the commands before you run them. The explanation is generated, and grounded on the reference notes shown beside it, but it can still be wrong about your specific setup. The matched reference entry is the authoritative part.
Related tools
Translating a single command is faster with the command converter. For a whole stack, the Compose migration analyser reports every field that will not survive the move and generates a startup script. The command reference lists the noun-first equivalents.
Frequently asked questions
- Why does my Docker command fail under wslc?
- Usually because the flag genuinely does not exist. On wslc 2.9.4.0 the rejected ones are
--restart,--deviceand--platform;--network hostis recognized but refused. Note that--gpusand the--health-*flags DO exist, andwslc psworks as an alias ofwslc list. Paste the error above and the analyser names the specific limitation. - Is this just a general-purpose AI chatbot?
- No. Every answer is grounded on a fixed set of documented wslc failure modes kept in this site's repository. The matched reference entry is shown alongside the generated diagnosis so you can check the advice against it. An ungrounded model tends to answer wslc questions with Docker advice that does not apply, because wslc is a preview with little public training data.
- Why does it say "Could not find a valid Docker environment"?
- That is Testcontainers, or another Docker API client, failing to locate a daemon. wslc has no dockerd, no
/var/run/docker.sockand no Engine API, so no configuration will satisfy it. You need a Docker-compatible runtime for those tools. - Is my error output stored?
- No. The text is sent to the diagnosis endpoint, used for that one request, and not written to any store or log by this site. There is a per-IP rate limit on the endpoint, which records only a request timestamp.