-
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
SSH command to podman machine does not work if using applehv #21090
Comments
Interested in opening a PR to fix? |
In theory yes. Practically, this is not a good opportunity because I am a Java developer with scripting capabilities (who did not get attracted each time he started reading some go). If you have hints how this should be fixed, you can share it here in case I have a colleague that wants to get started. |
The same issue.
|
i have a fix for this , but it is somewhat layered. |
small correction to properly lookup a applehv vm on disk. Fixes: containers#21090 [NO NEW TESTS NEEDED] Signed-off-by: Brent Baude <baude@redhat.com>
There is a bug in the fix.
|
If a command is specified in arg[0], an error occurs in the following part and the command is not added to sshOpts.Args. podman/pkg/machine/applehv/config.go Lines 63 to 65 in de797e5
|
small correction to properly lookup a applehv vm on disk. Fixes: containers#21090 [NO NEW TESTS NEEDED] Signed-off-by: Brent Baude <baude@redhat.com>
Issue Description
I switched from
qemu
toapplehv
by editing/Users/<user>/.config/containers/containers.conf
:podman machine ssh date
does not work (while podman machine ssh does work).Steps to reproduce the issue
Steps to reproduce the issue
podman machine ssh date
Describe the results you received
Describe the results you expected
Result of the date command inside the podman machine
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: