slimtoolkit / slimtoolkit/slim
Can't mount windows paths | or how to mount?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 841
- PR merge metrics
- No merged PRs in 30d
Description
Running Windows 11 24H2
using containerized slim
Expected Behavior
Mounting is working normal on Windows paths
Actual Behavior
Not working at all.
Steps to Reproduce the Problem
- Make a container
docker build -t container_name . - Run slim with mount
docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock dslim/slim build --http-probe=false --mount "type=bind,source=D:\TEMP\container_data,target=/app/container_data" container_name
Specifications
- Version: slim version linux/amd64|Transformer|1.40.11|1b271555882eacdfb4e6598d6d0552e9b9b1449b|2024-02-02_01:36:22PM
- Platform: Windows 11 24H2
Running Windows 11 24H2
Server: Docker Desktop 4.37.1 (178610)
Engine:
Version: 27.4.0
WSL:
Version WSL: 2.3.26.0
Kernel version: 5.15.167.4-1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported slim build command with its Windows bind-mount source and review the CLI handling for --mount values. Done means the documented Windows path mounts successfully, or the command clearly reports the supported syntax or limitation; verify with the Docker Desktop versions listed in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100