> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/users/client/wsl.md).

# Windows Subsystem for Linux

The usage of StrongDM CLI with Windows Subsystem for Linux (WSL) is not supported. However, WSL1 often works well with StrongDM and WSL2 can often be made to work via manual configuration.

You can manually configure your `/etc/wsl.conf` to run systemd each time WSL starts, which will cause sdm to start:

```
[boot]
systemd=true
```

{% hint style="info" %}
If your version of WSL is not up to date, or not the Windows Store version, systemd may not run on WSL. If this is the case, you can also try configuring `sdm start` to run directly:

```
[boot]
  command="/etc/init.d/sdm start"
```

{% endhint %}

Additionally, when setting up WSL2, if you want to be able to connect to anything within WSL2 from Windows, you can `echo "export SDM_DOCKERIZED=true" >> ~/.bashrc"` so that `SDM_DOCKERIZED=true` is set any time the WSL2 instance is restarted.

These two adjustments may help with WSL2, but currently no version of WSL is officially supported.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.strongdm.com/users/client/wsl.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.