Please enable JavaScript to view this site.

Navigation: Take Command

WSL and Container Profiles

Scroll Prev Top Next More

Take Command can use a WSL, Docker, or Podman profile to open a terminal in an installed WSL distribution or an already-running local container. These profiles use ordinary Take Command ConPTY tabs, not a separate terminal window.

 

Before you begin

 

Profile type

Requirement

WSL

An installed, registered WSL distribution and wsl.exe.

Docker

A running container accessible through the local Docker named pipe and docker.exe installed on a local drive. A remote Docker context is not used.

Podman

A running container in the default local Podman machine, with podman.exe installed on a local drive. The machine connection must use local loopback; a remote connection cannot be selected.

 

Docker and Podman container images must provide /bin/sh. Take Command opens a shell in a running container; it does not create or start containers.

 

Create and open a profile

 

1.Open Connections > Connection Manager (or Settings > Profiles).

2.Add a profile, give it a recognizable Name, and choose WSL, Docker, or Podman from Type.

3.Select Refresh / Discover. Discovery is not automatic when the page opens. Select the distribution or running container from Target.

4.Optionally set a Title, Group, or other visual preferences. For WSL, you may also set Directory as described below. Leave Directory empty for containers.

5.Apply the settings, then open the profile from the profile menu. Changes to a profile affect new tabs, not tabs that are already open.

 

The container picker displays a name and shortened ID when available, but the profile stores the full container ID. Applying a profile and opening its tab both check that its target is still available. If the container is replaced, select the new one with Refresh / Discover and apply the change again.

 

Starting directory

 

Leave a WSL profile's Directory blank to start in the distribution's home directory. To start elsewhere, use a UNC path within the selected distribution, for example:

 

\\wsl.localhost\Ubuntu\home\alice\projects

 

The \\wsl$\Ubuntu\... form is also accepted. Take Command maps the path to the corresponding Linux path for that distribution. Windows drive paths, paths into a different distribution, and unsafe relative components are rejected; they are not guessed or silently translated.

 

Container starting directories are not supported. A host directory is not automatically mounted or mapped into a container. Use the container runtime's own explicit configuration if the container needs access to host files.

 

What the tab shows

 

The tab displays [WSL:distribution], [Docker:short-ID], or [Podman:short-ID] based on the selected, validated profile target. An unavailable session may show :off. The badge is not inferred from shell output or an application-supplied terminal title. In split tabs, the badge describes the focused pane. [ADMIN] does not describe privileges inside WSL or a container.

 

You can also reference a typed profile from a startup tab without setting a separate startup-tab command. As with an ordinary typed profile, startup-tab command, credential, and elevation overrides are not supported.

 

Safety and limitations

 

•These profile types do not accept a custom launch command, Run As, password or vault secret, or elevated-tab override. Use a Local profile if you need a custom command instead.

•Take Command does not add mounts, forward agents or credentials into the target, or launch a container on a remote Docker/Podman host. Podman uses the locally configured machine identity to connect to that local machine.

•Docker uses the local named pipe even if another Docker context or DOCKER_HOST is configured. Podman requires a default local machine connection rather than an arbitrary configured remote destination.

 

Troubleshooting

 

Symptom

What to check

Refresh / Discover finds no WSL distribution.

Check that the distribution is installed for your Windows account and that wsl.exe is available.

Docker discovery fails.

Confirm Docker is installed, its local daemon is running, and the local Docker named pipe is reachable. A remote Docker context alone is insufficient.

Podman reports that the default connection is not a local machine.

Start the Podman machine and make its local machine connection the default; a remote connection is deliberately rejected.

A container is missing or the target is unavailable at launch.

Start the container, refresh discovery, select it again if its ID changed, and apply the profile.

The container tab opens but the shell exits.

Check that the selected running container includes /bin/sh; Take Command uses exec -it to start it.

The starting directory is rejected.

For WSL, use a UNC path under the selected distribution. For Docker or Podman, clear Directory.

Applying a profile reports an override error.

Clear Command, Run As, password/secret, and elevated options; typed profiles derive the command from the selected target.