Bug description
Adding a podman remote with ssh connection should list the images and pods in the podman desktop but this is not working
Operating system
Windows 11
Installation Method
Installer from website/GitHub releases
Version
latest-nightly - https://github.com/containers/podman-desktop/releases/tag/v1.12.0-202408052012-7c3c5ee
Steps to reproduce
- Install PD from nightly (which is available for releases)
- Run podman setup but don't start the podman machine (Just the installation part)
- Install the OpenShift Local extension
- From the
Setting => preference => Extension: podman => Enable the Remote
- Set the microshift preset from the openshift local configuration
- Start the openshift local wait till it started
From the windows powershell
> podman system connection add crc-root --identity "C:\Users\rhqp\.crc\machines\crc\id_ecdsa" "ssh://core@127.0.0.1:2222/run/podman/podman.sock"
> podman system connection add crc --identity "C:\Users\rhqp\.crc\machines\crc\id_ecdsa" "ssh://core@127.0.0.1:2222/run/user/1000/podman/podman.sock"
> podman system connection ls
Name URI Identity Default
crc ssh://core@127.0.0.1:2222/run/user/1000/podman/podman.sock C:\Users\rhqp\.crc\machines\crc\id_ecdsa false
crc-root ssh://core@127.0.0.1:2222/run/podman/podman.sock C:\Users\rhqp\.crc\machines\crc\id_ecdsa true
From windows CLI you can get the images and running pod using podman images / podman ps command.
Now check the PD and see if you can get those details from the UI but there is noting.
Relevant log output
From the Troubleshooting => logs didn't get any suspicious failure logs
↪️ Activating extension (podman-desktop.kind) ended in 579 milliseconds
main ↪️ Activating extension (podman-desktop.kube-context) with max activation time of 20 seconds
main ↪️ [kube-context] starting extension kube-context
main ↪️ Activating extension (podman-desktop.kube-context) ended in 2 milliseconds
main ↪️ Activating extension (podman-desktop.kubectl-cli) with max activation time of 20 seconds
main ↪️ Activating extension (podman-desktop.kubectl-cli) ended in 5 milliseconds
main ↪️ Activating extension (podman-desktop.lima) with max activation time of 20 seconds
main ↪️ [lima] Could not find socket at C:\Users\rhqp\.lima\podman\sock\podman.sock
main ↪️ Activating extension (podman-desktop.lima) ended in 5 milliseconds
main ↪️ Activating extension (podman-desktop.podman) with max activation time of 20 seconds
main ↪️ [kubectl-cli] Error getting kubectl from user PATH: Error: Failed to execute command: spawn kubectl.exe ENOENT, trying from extension storage path
main ↪️ [kubectl-cli] Error getting kubectl version system from extension storage path Error: Failed to execute command: spawn C:\Users\rhqp\.local\share\containers\podman-desktop\extensions-storage\podman-desktop.kubectl-cli\bin\kubectl.exe ENOENT
main ↪️ [podman] Error while pinging docker as podman Error: connect ENOENT //./pipe/docker_engine
main ↪️ [podman] Unable to run regex on containers.conf file. Reason: Error: ENOENT: no such file or directory, open 'C:\Users\rhqp\AppData\Roaming\containers\containers.conf'
main ↪️ Activating extension (podman-desktop.podman) ended in 1068 milliseconds
main ↪️ Activating extension (podman-desktop.registries) with max activation time of 20 seconds
main ↪️ Activating extension (podman-desktop.registries) ended in 1 milliseconds
main ↪️ Activating extension (redhat.openshift-local) with max activation time of 20 seconds
main ↪️ Activating extension (redhat.openshift-local) ended in 5687 milliseconds
main ↪️ PluginSystem: initialization done.
main ↪️ Skipping update for extension redhat.openshift-local because installed version 1.3.0 is greater or equal to latest available version 1.3.0
main ↪️ (node:11192) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'C:\Users\rhqp\.kube\config' at async open (node:internal/fs/promises:639:25) at async Object.readFile (node:internal/fs/promises:1249:14) at async wx.refresh (C:\Users\rhqp\AppData\local\Programs\podman-desktop\resources\app.asar\packages\main\dist\index.cjs:291:30135) at async wx.setKubeconfig (C:\Users\rhqp\AppData\local\Programs\podman-desktop\resources\app.asar\packages\main\dist\index.cjs:292:9124) at async C:\Users\rhqp\AppData\local\Programs\podman-desktop\resources\app.asar\packages\main\dist\index.cjs:291:25984 (Use `Podman Desktop --trace-warnings ...` to show where the warning was created)
main ↪️ (node:11192) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
main ↪️ [openshift-local] Error: Value '' for configuration property 'pull-secret-file' is invalid, reason: file '' does not exist
main ↪️ [openshift-local] Error: Value '' for configuration property 'pull-secret-file' is invalid, reason: file '' does not exist
main ↪️ [openshift-local] Logs tick: RequestError: connect ENOENT //?/pipe/crc-http
main ↪️ start watching services in context [object Object]
main ↪️ start watching ingresses in context [object Object]
main ↪️ start watching routes in context [object Object]
main ↪️ start watching configmaps in context [object Object]
main ↪️ start watching secrets in context [object Object]
main ↪️ start watching nodes in context [object Object]
main ↪️ start watching persistentvolumeclaims in context [object Object]
main ↪️ Kube deployment watch ended Error: aborted
Additional context
No response
Bug description
Adding a podman remote with ssh connection should list the images and pods in the podman desktop but this is not working
Operating system
Windows 11
Installation Method
Installer from website/GitHub releases
Version
latest-nightly - https://github.com/containers/podman-desktop/releases/tag/v1.12.0-202408052012-7c3c5ee
Steps to reproduce
Setting => preference => Extension: podman => Enable the RemoteFrom the windows powershell
From windows CLI you can get the images and running pod using
podman images/podman pscommand.Now check the PD and see if you can get those details from the UI but there is noting.
Relevant log output
Additional context
No response