Agent skill

Docker Via Wsl

by JMBeresford in JMBeresford/retrom

A skill your agent uses when YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command.

MITAuto-check passedDevOps & Cloud

Install Docker Via Wsl

skills CLI
$ npx skills add JMBeresford/retrom --skill docker-via-wsl -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JMBeresford/retrom docker-via-wsl --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JMBeresford/retrom.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/docker-via-wsl .claude/skills/docker-via-wsl && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
docker-via-wsl
GitHub stars
2.1k
Token cost
~832 tokens
SKILL.md length
330 words
Files
2 (incl. references)
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command.

  • YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command
  • SKILL.md covers When this applies, The problem, Why it matters and The rule, plus 1 more section
  • Calls docker
  • Mount source wrong

What it does

Docker Via Wsl is an agent skill from JMBeresford/retrom. Use when YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command. Docker Desktop runs on the WSL2 engine, so commands must be re-issued INSIDE WSL via wsl.exe -- running them from the Windows shell on a network/SMB drive (Z:, UNC) corrupts bind-mount paths. Does NOT apply if your shell is already inside WSL. Triggers on: docker, docker compose, docker-compose, container, bind mount, volume, 'is a directory', mount source wrong…

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/diagnosis-and-fix.md`). Compatibility notes: Windows host with Docker Desktop using the WSL2 backend.

It sits in DevOps & Cloud, covering Containers. It works with Docker, Bash, Git and PowerShell. The repository describes itself as: A centralized game library/collection management service with a focus on emulation. The licence is MIT.

When your agent uses it

  • YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command
  • Mount source wrong
  • Windows + Docker Desktop

Example prompts

  • “is a directory”
  • “/docker-via-wsl”

Requirements

  • Docker
  • Compatibility (from SKILL.md): Windows host with Docker Desktop using the WSL2 backend.
  • Pre-approved tools (allowed-tools): Bash(wsl.exe:*), Bash(docker:*), Bash(uname:*), Read, Glob, Grep

What it can do on your machine

Read from SKILL.md and the folder at commit c081a2d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(wsl.exe:*)
    • Bash(docker:*)
    • Bash(uname:*)
    • Read
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Windows host with Docker Desktop using the WSL2 backend.

    From compatibility in the SKILL.md frontmatter.

Context cost

Docker Via Wsl loads about 832 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 140 tokens; SKILL.md has 330 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~140
When it runs · the whole SKILL.md, loaded when a task matches
~832
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JMBeresford/retrom at commit c081a2d, republished under its MIT licence (© JMBeresford). 330 words, ~832 tokens.

Download SKILL.mdSave it as .claude/skills/docker-via-wsl/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
docker-via-wsl
description
Use when YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command. Docker Desktop runs on the WSL2 engine, so commands must be re-issued INSIDE WSL via wsl.exe -- running them from the Windows shell on a network/SMB drive (Z:, UNC) corrupts bind-mount paths. Does NOT apply if your shell is already inside WSL. Triggers on: docker, docker compose, docker-compose, container, bind mount, volume, 'is a directory', mount source wrong, Windows + Docker Desktop, WSL.
allowed-tools
Bash(wsl.exe:*), Bash(docker:*), Bash(uname:*), Read, Glob, Grep
compatibility
Windows host with Docker Desktop using the WSL2 backend.
license
(MIT AND CC-BY-SA-4.0)
metadata.version
1.10.0
metadata.repository
https://github.com/netresearch/docker-development-skill
metadata.author
Netresearch DTT GmbH

Docker via WSL (Windows)

When this applies

This applies when you, the AI agent, are running on a Windows host and your shell is OUTSIDE WSL -- your Bash tool is Git Bash/MSYS (uname -s shows MINGW64…/MSYS…) or you are in PowerShell/cmd. The docker binary there talks to Docker Desktop, but the daemon and its filesystem live in WSL2, so you must run commands inside WSL via wsl.exe.

If your shell is already inside WSL (uname -s shows Linux, native path /home/<user>/...), this skill does not apply -- run docker directly.

The problem

On Windows, Docker Desktop's daemon runs inside the WSL2 VM. Issue every docker command -- run, build, exec, pull, push, volume, network, inspect, compose, … -- from inside WSL, against a native Linux path. Never from a Windows shell (Git Bash/MSYS/PowerShell), especially on a mapped network/SMB drive (Z:, UNC \\host\share).

Why it matters

Driving Docker from a Windows shell whose CWD is on a network share forces Docker Desktop to translate the Windows bind path (e.g. Z:\proj\config) into a VM path. On SMB/UNC drives this is unreliable: it can duplicate a path segment (e.g. …/user/user/proj/config), so Docker mounts a wrong, empty directory and auto-creates the missing bind source as an empty directory. A file the container expects (init.sql, a config file) then appears as a directory -> could not read from input file: Is a directory. Your editor writes still land on the correct path via the share, so host and container views silently diverge.

This is NOT a Docker cache bug nor a "single-file bind mounts are fragile" problem (single-file binds work fine from WSL). The root cause is piloting Docker from Windows/SMB instead of from WSL.

The rule

Run any Docker command through WSL, in a native Linux path:

bash
wsl.exe -e bash -lc "cd /home/<user>/<project> && docker compose up -d"
wsl.exe -e bash -lc "docker ps"
wsl.exe -e bash -lc "docker build -t myimg /home/<user>/<project>"

Keep the project on the Linux filesystem the WSL distro sees natively (/home/<user>/...), not browsed through the Windows drive letter.

Diagnosis and fix

See references/diagnosis-and-fix.md for inspecting the mounted path, comparing host vs container views, and cleaning up a phantom bind directory.

© JMBeresford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/docker-via-wsl of JMBeresford/retrom.

  • SKILL.md
  • references/diagnosis-and-fix.md

Open the folder on GitHubat commit c081a2d

Compare with similar skills

Docker Via Wsl next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Docker Via Wsl compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Docker Via Wsl this skillJMBeresford/retrom2.1k—~832Automated safety check: PassMIT
Rtk Skillsopaco/deepwiki-rs3.1k—~1.4kAutomated safety check: PassMIT
Headless Codex CLI AutomationXiaomiMiMo/MiMo-Code14k—~2.7kAutomated safety check: PassMIT
Deploy Playgroundobjeck/objeck-lang164—~2.1kAutomated safety check: WarnCustom licence
Skillshare DevcontainerJetBrains/skills3661 repos~2kAutomated safety check: PassNone
Ssh Skillbadseal/ssh-skill538—~2.4kAutomated safety check: NotesNone

Similar skills

  • Rtk Skill

    sopaco/deepwiki-rs

    A skill your agent uses when running shell commands that produce verbose output (git, test, build, lint, package managers, docker).

    3.1k GitHub stars~1.4k tokensUpdated 26 days ago
    DevOps & CloudAuto-check passed
  • Headless Codex CLI Automation

    XiaomiMiMo/MiMo-Code

    Runs OpenAI Codex CLI as a non-interactive worker for CI, Docker, Kubernetes or remote servers, with sandbox modes and JSONL-friendly output.

    14k GitHub stars~2.7k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Deploy Playground

    objeck/objeck-lang

    Deploy/refresh the Objeck web playground (playground.objeck.org) on its VPS over SSH — git pull, rebuild the sandbox Docker image, restart the service, health-check.

    164 GitHub stars~2.1k tokensUpdated today
    DevOps & CloudAuto-check: warnings
  • Skillshare Devcontainer

    JetBrains/skills

    Official

    Run CLI commands, tests, and debugging inside the skillshare devcontainer.

    366 GitHub starsUsed in 1 repo~2k tokens
    Frontend & DesignAuto-check passed
  • Ssh Skill

    badseal/ssh-skill

    A skill your agent uses when a task requires SSH or SCP/SFTP behavior, a remote server, server alias/IP/hostname/user@host, bastion or jump-host access, remote command execution, upload/download…

    538 GitHub stars~2.4k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes
  • Swig CI Repro

    swig/swig

    Reproduce a GitHub Actions Linux CI failure locally when it does not happen on your machine: a podman/docker image that mirrors the ubuntu-22.04 runner by reusing the real Tools/CI-linux-.sh install…

    6.3k GitHub stars~1.2k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed

More from JMBeresford/retrom

  • Rust Skills

    JMBeresford/retrom

    Comprehensive Rust coding guidelines with 265 rules across 26 categories.

    2.1k GitHub starsUsed in 1 repo~9.5k tokens
    Auto-check passed
  • Docker Development

    JMBeresford/retrom

    A skill your agent uses when working with ANY Docker task: writing Dockerfiles, configuring docker-compose/compose.yml, multi-stage builds, docker-bake.hcl, container security audits, .dockerignore…

    2.1k GitHub stars~1.1k tokensUpdated 6 days ago
    Auto-check: warnings

Categories

Questions about Docker Via Wsl

What does Docker Via Wsl do?

A skill your agent uses when YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command. Docker Via Wsl is an agent skill from JMBeresford/retrom. Use when YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command.

When should I use Docker Via Wsl?

Docker Via Wsl fits situations like: YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command; mount source wrong; windows + Docker Desktop.

How do I install Docker Via Wsl in Claude Code?

Run `npx skills add JMBeresford/retrom --skill docker-via-wsl -a claude-code`. Or copy the skill folder (.agents/skills/docker-via-wsl in JMBeresford/retrom) into .claude/skills/docker-via-wsl in your project. Claude Code loads it when a task matches its description.

How do I install Docker Via Wsl in Codex?

Run `npx skills add JMBeresford/retrom --skill docker-via-wsl -a codex`. Or copy the skill folder (.agents/skills/docker-via-wsl in JMBeresford/retrom) into .agents/skills/docker-via-wsl in your project. Codex loads it when a task matches its description.

Can I use Docker Via Wsl in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JMBeresford/retrom --skill docker-via-wsl -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docker-via-wsl, .gemini/skills/docker-via-wsl, .github/skills/docker-via-wsl and .opencode/skills/docker-via-wsl in your project.

What does Docker Via Wsl need to run?

Going by SKILL.md and its folder, Docker Via Wsl needs the command-line tools its instructions call (docker). Our summary lists: Docker. Its frontmatter pre-approves these tools: Bash(wsl.exe:*), Bash(docker:*), Bash(uname:*), Read, Glob, Grep. Compatibility (from SKILL.md): Windows host with Docker Desktop using the WSL2 backend..

Does Docker Via Wsl access the network?

SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Docker Via Wsl safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Docker Via Wsl use?

Docker Via Wsl is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Docker Via Wsl use?

About 832 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 433 tokens, read only when the agent opens those files.

What are the alternatives to Docker Via Wsl?

Skills that share tags, products or a category with Docker Via Wsl: Rtk Skill (sopaco/deepwiki-rs, 3.1k stars), Headless Codex CLI Automation (XiaomiMiMo/MiMo-Code, 14k stars), Deploy Playground (objeck/objeck-lang, 164 stars) and Skillshare Devcontainer (JetBrains/skills, 366 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docker Via Wsl?

JMBeresford (a GitHub user) maintains it in JMBeresford/retrom, which has 2,099 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 4, 2026.

Source: JMBeresford/retrom on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.