-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows, mounting host dirs: Error: statfs /c/tmp/my-build/something: no such file or directory #14414
Comments
FYI @bmaxwell |
@n1hility PTAL |
@Karm thanks! -v /home/quicklab/quarkus-native/target/quarkus-native-1.0.0-native-image-source-jar:/project:z |
@bmaxwell @Karm I’m away today but I will take a look when I get a chance. On Windows the issue is probably the extra leading / “//c/tmp” that the native image builder is using. I can look at patching both sides. On Mac as of 4.1 the user home is automatically mounted into the VM for newly created machines, so -v should be working on any path within that |
@n1hility Oh, O.K., it seems that was it. Thx. It seems all right now:
I will see to it on the Quarkus side then. |
@Karm cool I will look at improving this on the podman side as well, collapse leading slashes into 1 (a single forward slash should work) |
/kind bug
Description
We would like to use Podman for Windows developer experience, using Linux containers to build our Java applications via Quarkus framework. We are driving the container runtime so as it exposes local project dirs to the container so as the container could operate on those files, e.g. to compile them using the compiler from the container image.
Steps to reproduce the issue:
The following reproducer requires some Java 11+ installed on the Windows machine. It also requires WSL2 backed Podman installed according to this guide: podman-for-windows.md
I am using cmder terminal for my convenience, but the issue is the same with e.g. PowerShell.
Describe the results you received:
Describe the results you expected:
Local project files on the host accessible by the running container. Build should complete normally as it does on a Linux host with podman.
Additional information:
It used to work just fine with Docker Desktop back in the day.
Version:
Is there something we could add as an argument to the podman command to make this work on Windows?
The text was updated successfully, but these errors were encountered: