With remote service, podman run --mount complains that path does not exist on client. #8473
Labels
Good First Issue
This issue would be a good issue for a first time contributor to undertake.
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
With a remote connection defined, invoke
podman run
with the--mount
option and it complains that the source path does not exist. True, but I am using a connection to remote host, so I would expect it to understand that the path in question is on the remote host, not the client.Steps to reproduce the issue:
podman system connection add --identity ~/.ssh/id_rsa microvm nfiedler@192.168.1.128
podman run --name=minio -d -e MINIO_ACCESS_KEY=minio -e MINIO_SECRET_KEY='keyboard cat' --publish '9000:9000' --mount type=bind,source=/mnt/tank/packs,destination=/data minio/minio --compat server /data
Describe the results you received:
Describe the results you expected:
No error reported, and the container would be running on the remote host.
Additional information you deem important (e.g. issue happens only occasionally):
Happens every time.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Recent versions: No. Looked at the changelog and this issue is not included among the 2.2.x changes.
Troubleshooting: Yes, nothing there about this.
Additional environment details (AWS, VirtualBox, physical, etc.):
MacBook Pro 15 inch 2018, podman service running in MicroOS from 3 days ago (no lsb_release or /etc/release?) in VirtualBox 6.1.16. I can run the same command from the shell in MicroOS and it succeeds, as expected.
The text was updated successfully, but these errors were encountered: