[2459820363] Upstream Reporter: sprig
Upstream issue status: Open
Upstream description:

Issue Description

Running on macos 14.6:

$ podman --log-level=trace system connection add host ssh://user@host
INFO[0000] podman filtering at log level trace
DEBU[0000] Found SSH_AUTH_SOCK "/private/tmp/com.apple.launchd.LtDz5CJvJ7/Listeners", ssh-agent signer enabled
DEBU[0000] SSH Agent Key SHA256:<key-id> ssh-rsa
DEBU[0000] SSH Agent Key SHA256:<another-id> ssh-rsa-cert-v01@openssh.com
WARN[0000] ssh host key mismatch for host host:22, got key SHA256:<third-id> of type ecdsa-sha2-nistp256
Error: failed to connect: ssh: handshake failed: knownhosts: key mismatch

whereas

$ ssh host
user@host ~ ${noformat}
h3. {anchor:steps-to-reproduce-the-issue}Steps to reproduce the issue
See above.

h3. {anchor:describe-the-results-you-received}Describe the results you received
See above.

h3. {anchor:describe-the-results-you-expected}Describe the results you expected
I expect the connection to be established. I expect to see where podman looks for host keys in the debug log so that I can confirm/remedy. In case of another problem \(not ssh related) I expect to be notified of this appropriately

h3. {anchor:podman-info-output}podman info output
{code:yaml}
Macos 14.6


$ podman info
OS: darwin/arm64
provider: applehv
version: 5.1.2

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: Get "http://d/v5.1.2/libpod/_ping": dial unix /var/folders/vx/wq1n25gs5t54v4sp3_6yj3c00000gn/T/storage-run-501/podman/podman.sock: connect: no such file or directory
{code}
\(note - I intentionally did not start the VM)

1. 1. 1. Podman in a container

No

1. 1. 1. Privileged Or Rootless

Rootless

1. 1. 1. Upstream Latest Release

Yes

1. 1. 1. Additional environment details

Additional environment details

1. 1. 1. Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

[EDIT]

I just checked the releases and saw 5.2.0 was available. Upgraded. Exactly the same results.