Seed CLI does not bind mount paths correctly when using Windows to create a Linux container

[mattbanderson]

Description
When using Seed CLI on Windows to build a Linux Docker container, seed run does not bind mount input files to a valid path in the container.

Reproduction Steps
Steps to reproduce the problem:

1. On a Windows computer, follow the steps in the Seed CLI tutorial
2. At the Run step, note the output of the bind mount in the docker run command.
3. Seed CLI attempts to bind mount a Windows path (C:\some\path\to\file) to a Windows path inside the container.

Expected behavior
Seed CLI should detect the operating systems involved and build operating system-specific paths.

Screenshots

Configuration Files
seed.manifest.json
Dockerfile

Version and Environment Details

• OS: Windows 10 build 19041
• Seed CLI: 1.2.1
• Docker: 19.03.08

[cshamis]

Windows support is a “nice to have” not a hard requirement. If it’s just a matter of changing an API call or two in go.lang to hit the OS specific path constructors to get it to work, so be it.

…

On Jul 7, 2020, at 4:37 PM, Matt Anderson ***@***.***> wrote:  Description When using Seed CLI on Windows to build a Linux Docker container, seed run does not bind mount input files to a valid path in the container. Reproduction Steps Steps to reproduce the problem: On a Windows computer, follow the steps in the Seed CLI tutorial At the Run step, note the output of the bind mount in the docker run command. Seed CLI attempts to bind mount a Windows path (C:\some\path\to\file) to a Windows path inside the container. Expected behavior Seed CLI should detect the operating systems involved and build operating system-specific paths. Screenshots Configuration Files seed.manifest.json Dockerfile Version and Environment Details OS: Windows 10 build 19041 Seed CLI: 1.2.1 Docker: 19.03.08 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[mattbanderson]

After testing Seed CLI in WSL 2 and native Windows, Seed CLI in WSL 2 is the preferred approach. I agree this is a nice-to-have, not a bug.

If native Windows support becomes a priority in the future, then we would need to re-visit this.