PD reported an issue that the new connection update prompt just hangs for them, while they could set the --update-connection=false flag that would fail on older podman version without that flag.

The reason the prompt hangs is because the command they spawn attached a pipe on stdin/our/err so stdin is not at EOF and as such our read blocks forever.

The simple fix here is to make sure stdin is a tty before prompting.

Other options would be to provide an env var that PD can set to disable the prompt or simply never prompt and just only update when --update-connection is set by a user.