Support native source folder for volume mount in remote model

[jeffwubj]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Description

Currently, looks like in podman's remote client case, bind volume will use source folders on podman server's host, could we support (or give some configurations to choose) using source folders on podman client's host?

podman client and podman server may run in different hosts, or one runs in the host, the other runs in a VM. Have the ability to mount folders on the client side might be able to open more use cases...

[afbjorklund]

I think this also happens, when using docker to connect to a remote server (rather than using the Docker Desktop product) ?
In Docker Toolbox (docker-machine), they worked around this issue by sharing the entire home folder (!) using vboxsf...

You should be able to create network volumes using podman volume, but I am a little uncertain about the syntax to use.
It takes a --driver parameter, which only talks about the default "local" driver that uses regular directories on the host.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

I am not sure how we would make this work, other then to export the current directory to the server running podman via nfs, samba or some other network protocol and then volume mount that directory into the container.

I am not sure is sshfs has this type ability, to share your homedir with a remote machine?

[afbjorklund]

I am not sure is sshfs has this type ability, to share your homedir with a remote machine?

The way we used sshfs in docker-machine, was to share the remote machine with a local mount.

https://docs.docker.com/machine/reference/mount/

That is, the mount was going in the other direction. Used sftp on the remote and fuse on the local.

Other than that, it was just VirtualBox shared folders...

[nlfiedler]

May I suggest that the issue is that podman is validating the mount points on the local side, rather than on the remote side? I'm running on macOS and deploying to a Linux host, on which the mount points exist. Maybe if podman client were to not validate the paths when connecting to a remote service, then it would just work?

[mheon]

That sounds like a separate issue? This one is about emulating a Docker behavior where folders from an OS X host are able to be mounted into containers on the Linux VM running containers. What you're describing is definitely separate (but definitely a bug, and I encourage you to file an issue about it).

…

On Tue, Nov 24, 2020 at 9:57 PM Nathan Fiedler ***@***.***> wrote: May I suggest that the issue is that podman is validating the mount points on the local side, rather than on the remote side? I'm running on macOS and deploying to a Linux host, on which the mount points exist. Maybe if podman client were to not validate the paths when connecting to a remote service, then it would just work? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8016 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3AOCCW773SGH72W3WGX23SRRXBVANCNFSM4SQV632Q> .

[nlfiedler]

Ah, you're right, I was seeing what I wanted to see. I've filed another issue, thanks.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

This issue is not stale, but no one is currently working on it.