Missing all running containers, images, etc

[mpiggott]

I've had a working rootless podman cli setup on Fedora for a while, however when I installed Podman Desktop the UI is empty, i.e. running containers are never shown.

I'm assuming this isn't expected but I haven't seen an error message and the UI reports podman as running.

[benoitf]

Hello @mpiggott

What's the version of Podman on your Fedora ?
And are you using the flatpak package of Podman Desktop on your setup ?

Podman Desktop is connecting to the REST API/socket of your Podman installation using /run/user/<the-user-uid>/podman/podman.sock path

you may try to see what your installation is reporting when performing the REST API call:
curl --unix-socket /run/user/<the-user-uid>/podman/podman.sock "http:/v1.41/containers/json?all=true"

[mpiggott]

Hi @benoitf

I'm using podman 4.3.1 and the flatpak distribution for podman-desktop (I didn't find it via dnf).

Using curl I do see the list of containers that I'd expected to see with podman-desktop.

Also in Podman Desktop under Settings > Resources > Podman > Podman I see status:started and Socket: /run/user/1000/podman/podman.sock (1000 is my user id)

[benoitf]

hello @mpiggott could you restart Podman Desktop (killing it or using File/(quit|exit) menu first (at some point it was only hiding the window)
Even after a restart you don't see any containers ?
if it's still the case, could you look at if something is displayed when you go in the DevConsole
View / Toggle Developer Tools and then console

[mpiggott]

I actually installed podman-desktop a couple weeks ago and have restarted since for unrelated reasons. I have killed the podman-desktop application but there is no change.

From the devtools console:

index.ts:921 main ↪️ APPIMAGE env is not defined, current application is not an AppImage
(anonymous) @ index.ts:921
index.ts:921 main ↪️ Kubeconfig path /home/mpiggott/.kube/config provided does not exist. Skipping.
(anonymous) @ index.ts:921
index.ts:921 main ↪️ Activating extension (crc)
index.ts:921 main ↪️ [crc] Can not find CRC binary!
(anonymous) @ index.ts:921
index.ts:921 main ↪️ Activation extension (crc) ended
index.ts:921 main ↪️ Activating extension (docker)
index.ts:921 main ↪️ Activation extension (docker) ended
index.ts:921 main ↪️ Activating extension (kube-context)
index.ts:921 main ↪️ [kube-context] starting extension kube-context
index.ts:921 main ↪️ Activation extension (kube-context) ended
index.ts:921 main ↪️ Activating extension (lima)
index.ts:921 main ↪️ [lima] Could not find podman socket at /home/mpiggott/.lima/podman-lima/sock/podman.sock nor /home/mpiggott/.lima/podman-lima/sock/podman.sock
(anonymous) @ index.ts:921
index.ts:921 main ↪️ Activation extension (lima) ended
index.ts:921 main ↪️ Activating extension (podman)
index.ts:921 main ↪️ Activation extension (podman) ended
index.ts:921 main ↪️ PluginSystem: initialization done.
index.ts:921 main ↪️ Autostarting container engine
index.ts:921 main ↪️ (node:3) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/run/user/1000/containers/containers.conf'
(Use `podman-desktop --trace-warnings ...` to show where the warning was created)
(anonymous) @ index.ts:921
index.ts:921 main ↪️ (node:3) 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: 1)
(anonymous) @ index.ts:921
index.ts:921 main ↪️ PluginSystem: received dom-ready event from the UI
index.ts:921 main ↪️ Delayed startup, flushing 5 events
index.ts:921 main ↪️ error is Error: getaddrinfo ENOTFOUND unix
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)
4index.ts:921 main ↪️ error in engine Podman Error: getaddrinfo ENOTFOUND unix
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)

[benoitf]

ok so it seems we got an error

 UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/run/user/1000/containers/containers.conf'

[benoitf]

and

ndex.ts:921 main ↪️ error is Error: getaddrinfo ENOTFOUND unix
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)

[benoitf]

Could you try with a pre-release artifact https://github.com/containers/podman-desktop/releases/download/untagged-8ccb59e1720003e470ad/podman-desktop-0.0.202301111441-430b081.flatpak
or with a binary-only version (not using flatpak): https://github.com/containers/podman-desktop/releases/download/untagged-8ccb59e1720003e470ad/podman-desktop-0.0.202301111441-430b081.tar.gz

[mpiggott]

These files weren't available when I tried earlier, so I used v0.0.202301111448-1518bd6 which was the latest. The flatpak seems to have the same errors.

Running the tarball from the cli I saw a large number of errors at the console:

(node:175900) 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: 46)
(node:175900) UnhandledPromiseRejectionWarning: Error: EACCES: permission denied, watch '/var/run/systemd/journal/streams/8:1028700'
    at FSWatcher.<computed> (node:internal/fs/watchers:244:19)
    at Object.watch (node:fs:2301:34)
    at createFsWatchInstance (/home/mpiggott/Downloads/podman-desktop/podman-desktop-0.0.202301111448-1518bd6/resources/app.asar/node_modules/chokidar/lib/nodefs-handler.js:119:15)
    at setFsWatchListener (/home/mpiggott/Downloads/podman-desktop/podman-desktop-0.0.202301111448-1518bd6/resources/app.asar/node_modules/chokidar/lib/nodefs-handler.js:166:15)
    at NodeFsHandler._watchWithNodeFs (/home/mpiggott/Downloads/podman-desktop/podman-desktop-0.0.202301111448-1518bd6/resources/app.asar/node_modules/chokidar/lib/nodefs-handler.js:331:14)
    at NodeFsHandler._handleFile (/home/mpiggott/Downloads/podman-desktop/podman-desktop-0.0.202301111448-1518bd6/resources/app.asar/node_modules/chokidar/lib/nodefs-handler.js:395:23)
    at NodeFsHandler._addToNodeFs (/home/mpiggott/Downloads/podman-desktop/podman-desktop-0.0.202301111448-1518bd6/resources/app.asar/node_modules/chokidar/lib/nodefs-handler.js:637:21)

(there were a number of /var/run/... paths with similar errors)

Also a bunch of these:

(node:175900) 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: 122)
(node:175900) UnhandledPromiseRejectionWarning: Error: ELOOP: too many symbolic links encountered, stat '/var/run/udev/watch/16'

I have a log but its about 200kb

[mpiggott]

Oh, I should specify - the CLI errors were via stderr on the terminal console not the devtools console :)