slim icon indicating copy to clipboard operation
slim copied to clipboard

Can't mount windows paths | or how to mount?

Open MrMarvel opened this issue 1 year ago • 2 comments

Running Windows 11 24H2 using containerized slim

Expected Behavior

Mounting is working normal on Windows paths


Actual Behavior

Not working at all.

image


Steps to Reproduce the Problem

  1. Make a container docker build -t container_name .
  2. 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

MrMarvel avatar Dec 23 '24 17:12 MrMarvel

@MrMarvel this would be a pretty sweet enhancement to add support for Windows paths. There's a number of places where Unix paths are assumed and constructed instead of using generic file path manipulation instructions. The main blocker for me is not having a Windows environment to test the enhancements :-) If anybody has ideas how to solve it in a creative way I'm happy to explore different options.

kcq avatar Feb 13 '25 19:02 kcq

If anybody has ideas how to solve it in a creative way I'm happy to explore different options.

Yes.

MrMarvel avatar Feb 20 '25 12:02 MrMarvel