Relative volume path in Kube yaml is not resolved

[Fodoj]

For example:

  volumes:
    - name: app
      hostPath:
        path: ./
        type: Directory

Will result in volume simply ignored. Podman 1.3.0-dev, Fedora Workstation 29.

[haircommander]

@Fodoj just to make sure, are you expecting the path to be based on the kube yaml location?

[Fodoj]

Good question... I think that would make more sense than relative to where podman runs from, but no idea what's the way to go, really

[haircommander]

podman --mount type=bind,src=./,target=/tmp -ti alpine ls /tmp
actually mounts based on the rundir. I'd likely want to line up functionality with that, as that's the equivalent from the podman CLI. WDYT @Fodoj
(cc: @mheon because you just did some mount reworking and may have something to say here)

[mheon]

Relative mounts working right now are honestly more of an accident than anything. I don't think we consider them supported, so if we want to change where they're relative to (such that they make more sense), I'd be fine with that. Directory Podman is being run from would seem to make the most sense to me.

(We'll probably have to resolve the relative paths before we pass them into Libpod to do this, but that's not a particularly big deal now that we have a common path for all mounts code)

[baude]

where do we stand

[haircommander]

@QiWang19 I seem to remember you doing work with resolving relative paths, is that the case?

[QiWang19]

I have this PR #3537 to convert the src path to absolute path

[haircommander]

I can confirm #3537 fixed this! thanks @QiWang19

[majidaldo]

this doesn't work on windows (from the outside). it does work if i use podman inside podman-machine-default inside wsl (which by default mounts the current dir).