You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the tutorial it is using an identity when creating the new remote connection, but this leads to be asked for the key passphrase.
I read somewhere that I should not set an identity so the connection would use my ssh agent, but it does not seem to be working on windows.
Steps to reproduce the issue
Prerequsite:
You should have a linux box with podman installed and running as rootless
Steps to reproduce the issue
Add a new connection
podman --remote system connection add remote ssh://myuser@mylinuxbox/run/user/1000/podman/podman.sock
List the existing connections
> podman --remote system connection list
Name URI Identity Default ReadWrite
podman-machine-default ssh://[email protected]:62876/run/user/1000/podman/podman.sock C:\Users\MyUser\.local\share\containers\podman\machine\machine true true
podman-machine-default-root ssh://[email protected]:62876/run/podman/podman.sock C:\Users\MyUser\.local\share\containers\podman\machine\machine false true
remote ssh://myuser@mylinuxbox:22/run/user/1000/podman/podman.sock false true
If I set an identity when creating the connection, then it asks for the key passphrase.
I also tried to explicit set $env:SSH_AUTH_SOCK="\.\pipe\openssh-ssh-agent", but then I have this error
> podman -c remote info --log-level=debug
time="2024-10-03T14:21:30+02:00" level=info msg="C:\\Program Files\\RedHat\\Podman\\podman.exe filtering at log level debug"
time="2024-10-03T14:21:30+02:00" level=debug msg="Called info.PersistentPreRunE(C:\\Program Files\\RedHat\\Podman\\podman.exe -c remote info --log-level=debug)"
time="2024-10-03T14:21:30+02:00" level=debug msg="Found SSH_AUTH_SOCK \"\\\\\\\\.\\\\pipe\\\\openssh-ssh-agent\", ssh-agent signer enabled"
time="2024-10-03T14:21:30+02:00" level=debug msg="Using Podman machine with `wsl` virtualization provider"
OS: windows/amd64
provider: wsl
version: 5.2.3
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: dial unix \\.\pipe\openssh-ssh-agent: connect: No connection could be made because the target machine actively refused it.
time="2024-10-03T14:21:30+02:00" level=debug msg="Shutting down engines"
But this was just a guess and I'm not sure it is relevant
The text was updated successfully, but these errors were encountered:
The issue mentioning the identity should not be set is #7806
and #15121 is kind of related but trying to connect to a WSL instance and not a remote, but I think this is relevant.
Issue Description
I was following the Podman remote-client tutorial and couldn't make it use the ssh agent.
In the tutorial it is using an identity when creating the new remote connection, but this leads to be asked for the key passphrase.
I read somewhere that I should not set an identity so the connection would use my ssh agent, but it does not seem to be working on windows.
Steps to reproduce the issue
Prerequsite:
You should have a linux box with podman installed and running as rootless
Steps to reproduce the issue
podman --remote system connection add remote ssh://myuser@mylinuxbox/run/user/1000/podman/podman.sock
Describe the results you received
podman is asking for the user password
Describe the results you expected
podman can connect without interaction
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
If I set an identity when creating the connection, then it asks for the key passphrase.
I also tried to explicit set $env:SSH_AUTH_SOCK="\.\pipe\openssh-ssh-agent", but then I have this error
But this was just a guess and I'm not sure it is relevant
The text was updated successfully, but these errors were encountered: