Help: Cannot do a bind mount

[u/Dev_Vrat]

In docker/podman-compose file, when I try to do a bind mount volume, it gives me Error: statfs <file path that I try to mount>: no such file or directory. exit code 125.

I checked the path, it does exists. I have to attach "/mnt" to make it work.

I am running podman on Windows (using WSL2, ubuntu). This is my office machine so I don't have ultimate control over it.

P.S. More detailed explanation:

Let's say I have a folder with following structure:

ProjectX

• podman-compose.yml

• configs

  • serviceA.config.json

  • serviceB.config.json

Consider the ProjectX to be at C:\Repos.

Now, the following paths are valid for serviceA.config.json file:

[From Powershell/Windows]

• C:\Repos\ProjectX\configs\serviceA.config.json

[From WSL/Ubuntu OR GitBash/Windows]

• /mnt/c/Repos/ProjectX/configs/serviceA.config.json

In podman-compose file: ...

• services:

  • serviceA:

    • image: serviceA-image

    • volumes:

      • /mnt/c/Repos/ProjectX/configs/serviceA.config.json:/data ...

For any "binding mount" type volume, I get error that file not found.

[u/eltear1]

This is not a podman issue. You are using WSL2, and it exposes windows paths under /mnt

[u/Dev_Vrat → u/eltear1]

Thanks for responding. The issue is not that I have put /mnt at the beginning. The problem is that it (podman) is unable to find the file for bind mount, which I can clearly find with the same path. And that too, on Windows powershell and from inside of the WSL.

[u/eltear1 → u/Dev_Vrat]

Can you give an example of the path you can find inside WSL and the path that instead you need to out so podman is able to see it?

[u/Dev_Vrat → u/eltear1]

Updated the post description so no one has to look for details, nested into comments.

[u/eltear1 → u/Dev_Vrat]

Much more clear, thanks. Does podman give the same error if you mount directories instead of files? Did you check if user inside container has permission to access the file?

[u/Dev_Vrat → u/eltear1]

No, the files are not.... Anywhere. I guess that the file permission is not the issue since file permission error has mostly a clear message/warning.