podman-desktop
podman-desktop copied to clipboard
containers
Authentication Extension Not Properly Loading (Unusable)
Bug description
When the Red Hat Authentication extension is added it does not actually show in the authentication providers list. I expect to see a login option to authenticate with Red Hat. Currently this is preventing me from using the bootc extension to build certain images from certain sources that require authentication.
Operating system
Fedora 42
Installation Method
Flathub (Linux)
Version
1.19.1
Steps to reproduce
- Install podman desktop (as flatpak through flathub or directly from GitHub releases) or run (by extracting the binaries from GitHub)
- Open podman desktop
- Select "Extensions"
- Select "Catalog"
- Scroll down and press the button to install the Red Hat Authentication extention
- Once installed, select the "Accounts" button
- Then select "Manage Authentication"
- You will notice that the Red Hat icon appears on the bottom toolbar, but there are no authentication providers listed. Refreshing the catalog does nothing.
Relevant log output
Additional context
No response
@HunterGerlach Hey, thanks for report. I noticed that once you have installed the extension, the drop down contains only one option: "Manage authentication". Which points to a problem with extension activation. If it was installed AND activated successfully, you would see two options, "Manage auth." and "Sign in with ..." like this:
This leads to a problem with extension, can you please open Extensions -> Installed Tab -> find Red Hat Authentication (will have probably some error state ), open Details and Error Tab, there should be an error which could help to identify the problem. You can also try to active the extension again if it is in error or disabled state.
If you could also provide a log from Troubleshooting (lightbuld in the status bar) -> Logs Or Gather Logs it could help to identify the problem.
The extension does not appear to be in an error state.
Below is the full (sanitized) log...
log : main ↪️ Starting http server to handle webviews on port 44000
log : main ↪️ System ready. Loading extensions...
log : main ↪️ Error while fetching API groups: FetchError: request to https://<CLUSTER_API_URL>/apis failed, reason: getaddrinfo ENOTFOUND <CLUSTER_API_URL>
log : main ↪️ Error while fetching API groups: FetchError: request to https://<CLUSTER_API_URL>/apis failed, reason: getaddrinfo ENOTFOUND <CLUSTER_API_URL>
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 1s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 1s.
log : main ↪️ Activating extension (podman-desktop.compose) with max activation time of 20 seconds
log : main ↪️ Activating extension (podman-desktop.compose) ended in 63 milliseconds
warn : MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 extensions-started listeners added. Use emitter.setMaxListeners() to increase limit
warn : MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 extension-stopped listeners added. Use emitter.setMaxListeners() to increase limit
warn : MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 extension-started listeners added. Use emitter.setMaxListeners() to increase limit
log : main ↪️ Activating extension (podman-desktop.docker) with max activation time of 20 seconds
log : main ↪️ Activating extension (podman-desktop.docker) ended in 8 milliseconds
log : main ↪️ Activating extension (podman-desktop.kind) with max activation time of 20 seconds
log : main ↪️ PluginSystem: received dom-ready event from the UI
log : main ↪️ Delayed startup, flushing 45 events
log : main ↪️ Fetched https://registry.podman-desktop.io/api/extensions.json in 211.565ms
debug : main ↪️ skip watching nodes in kubernetes context named "<KUBE_CONTEXT>", as the context is not reachable
debug : main ↪️ already watching deployments in kubernetes context named "<KUBE_CONTEXT>"
debug : main ↪️ already watching pods in kubernetes context named "<KUBE_CONTEXT>"
debug : main ↪️ skip watching services in kubernetes context named "<KUBE_CONTEXT>", as the context is not reachable
debug : main ↪️ skip watching ingresses in kubernetes context named "<KUBE_CONTEXT>", as the context is not reachable
debug : main ↪️ skip watching routes in kubernetes context named "<KUBE_CONTEXT>", as the context is not reachable
debug : main ↪️ skip watching persistentvolumeclaims in kubernetes context named "<KUBE_CONTEXT>", as the context is not reachable
debug : main ↪️ skip watching configmaps in kubernetes context named "<KUBE_CONTEXT>", as the context is not reachable
debug : main ↪️ skip watching secrets in kubernetes context named "<KUBE_CONTEXT>", as the context is not reachable
debug : main ↪️ skip watching jobs in kubernetes context named "<KUBE_CONTEXT>", as the context is not reachable
debug : main ↪️ skip watching cronjobs in kubernetes context named "<KUBE_CONTEXT>", as the context is not reachable
warn : main ↪️ [kind] Error getting full path Error: Command execution failed with exit code 1
log : main ↪️ [kind] kind extension is active
log : main ↪️ Activating extension (podman-desktop.kind) ended in 223 milliseconds
log : main ↪️ Extension (podman-desktop.kube-context) not activated because it is disabled
log : main ↪️ Extension (podman-desktop.kubectl-cli) not activated because it is disabled
log : main ↪️ Activating extension (podman-desktop.lima) with max activation time of 20 seconds
debug : main ↪️ [lima] Could not find socket at /home/<USER>/.lima/podman/sock/podman.sock
log : main ↪️ Activating extension (podman-desktop.lima) ended in 2 milliseconds
log : main ↪️ Activating extension (podman-desktop.podman) with max activation time of 20 seconds
log : main ↪️ [kind] kind extension is active
log : main ↪️ Activating extension (podman-desktop.podman) ended in 82 milliseconds
log : main ↪️ Activating extension (podman-desktop.registries) with max activation time of 20 seconds
log : main ↪️ Activating extension (podman-desktop.registries) ended in 1 millisecond
log : main ↪️ Activating extension (redhat.ai-lab) with max activation time of 20 seconds
log : main ↪️ [ai-lab] starting AI Lab extension
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 2s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 2s.
log : main ↪️ [kind] kind extension is active
log : main ↪️ Activating extension (redhat.ai-lab) ended in 104 milliseconds
log : main ↪️ PluginSystem: initialization done.
log : main ↪️ Autostarting podman-desktop.podman container engine
log : main ↪️ Skipping update for extension redhat.ai-lab because installed version 1.7.2 is greater or equal to latest available version 1.7.2
error : main ↪️ [ai-lab] Something went wrong while scanning cache. Error: ENOENT: no such file or directory, stat '/home/<USER>/.var/app/io.podman_desktop.PodmanDesktop/cache/huggingface/hub'
warn : main ↪️ [ai-lab] Can't find model info for local folder hf.ibm-granite.granite-3.3-8b-instruct-GGUF. Error: model is not loaded
error : main ↪️ [ai-lab] Something went wrong while scanning cache. Error: ENOENT: no such file or directory, stat '/home/<USER>/.var/app/io.podman_desktop.PodmanDesktop/cache/huggingface/hub'
error : main ↪️ [ai-lab] Something went wrong while scanning cache. Error: ENOENT: no such file or directory, stat '/home/<USER>/.var/app/io.podman_desktop.PodmanDesktop/cache/huggingface/hub'
log : main ↪️ [kind] kind extension is active
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 2s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 2s.
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 2s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 2s.
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 3s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 3s.
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 4s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 4s.
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
log : main ↪️ Telemetry request error: [object Object]
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 5s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 5s.
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 6s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 6s.
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 7s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 7s.
debug : main ↪️ Trying to watch pods on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 9s.
debug : main ↪️ Trying to watch deployments on the kubernetes context named "<KUBE_CONTEXT>" but got a connection refused, retrying the connection in 9s.
log : main ↪️ [redhat-authentication] REDHAT_AUTH_URL: https://<SSO_URL>/auth/realms/redhat-external/
log : main ↪️ [redhat-authentication] KAS_API_URL: https://api.openshift.com
log : main ↪️ [redhat-authentication] CLIENT_ID: podman-desktop
log : main ↪️ Activating extension (redhat.redhat-authentication) with max activation time of 20 seconds
log : main ↪️ [redhat-authentication] starting redhat-authentication extension
log : main ↪️ Activating extension (redhat.redhat-authentication) ended in 44 milliseconds
log : main ↪️ Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.
I think the interesting line is
Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.
For me the extension showed up in the Settings/Authentication after installing the extension, and I was able to log in, but after restarting my Fedora 42 I'm facing the same issue as @HunterGerlach. Here's my log:
error : main ↪️ Kubeconfig path /home/mbocek/.kube/config provided does not exist. Skipping.
log : main ↪️ Starting http server to handle webviews on port 44000
log : main ↪️ System ready. Loading extensions...
log : main ↪️ Activating extension (podman-desktop.compose) with max activation time of 20 seconds
warn : MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 extensions-started listeners added. Use emitter.setMaxListeners() to increase limit
warn : MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 extension-stopped listeners added. Use emitter.setMaxListeners() to increase limit
warn : MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 extension-started listeners added. Use emitter.setMaxListeners() to increase limit
log : main ↪️ Activating extension (podman-desktop.compose) ended in 44 milliseconds
log : main ↪️ Activating extension (podman-desktop.docker) with max activation time of 20 seconds
log : main ↪️ Activating extension (podman-desktop.docker) ended in 13 milliseconds
log : main ↪️ Activating extension (podman-desktop.kind) with max activation time of 20 seconds
log : main ↪️ PluginSystem: received dom-ready event from the UI
log : main ↪️ Delayed startup, flushing 22 events
error : main ↪️ [kind] Error: Command execution failed with exit code 1
error : main ↪️ [kind] Error: Command execution failed with exit code 1
log : main ↪️ Fetched https://registry.podman-desktop.io/api/extensions.json in 363.35413600000015ms
log : main ↪️ Fetched https://registry.podman-desktop.io/api/extensions.json in 61.194976ms
log : main ↪️ Fetched https://registry.podman-desktop.io/api/extensions.json in 169.93127000000004ms
log : main ↪️ [kind] kind extension is active
log : main ↪️ Activating extension (podman-desktop.kind) ended in 864 milliseconds
log : main ↪️ Activating extension (podman-desktop.kube-context) with max activation time of 20 seconds
log : main ↪️ [kube-context] starting extension kube-context
log : main ↪️ Activating extension (podman-desktop.kube-context) ended in 2 milliseconds
log : main ↪️ Activating extension (podman-desktop.kubectl-cli) with max activation time of 20 seconds
log : main ↪️ Activating extension (podman-desktop.kubectl-cli) ended in 68 milliseconds
log : main ↪️ Activating extension (podman-desktop.lima) with max activation time of 20 seconds
debug : main ↪️ [lima] Could not find socket at /home/mbocek/.lima/podman/sock/podman.sock
log : main ↪️ Activating extension (podman-desktop.lima) ended in 2 milliseconds
log : main ↪️ Activating extension (podman-desktop.podman) with max activation time of 20 seconds
log : main ↪️ [kind] kind extension is active
log : main ↪️ Activating extension (podman-desktop.podman) ended in 69 milliseconds
log : main ↪️ Activating extension (podman-desktop.registries) with max activation time of 20 seconds
log : main ↪️ Activating extension (podman-desktop.registries) ended in 1 milliseconds
log : main ↪️ Activating extension (redhat.ai-lab) with max activation time of 20 seconds
log : main ↪️ [ai-lab] starting AI Lab extension
warn : main ↪️ [kubectl-cli] Error getting kubectl from user PATH: Command execution failed with exit code 1: Command execution failed with exit code 1, trying from extension storage path
log : main ↪️ [kind] kind extension is active
warn : main ↪️ [kubectl-cli] Error getting kubectl version system from extension storage path Error: Command execution failed with exit code 1
log : main ↪️ [kind] kind extension is active
log : main ↪️ Activating extension (redhat.ai-lab) ended in 165 milliseconds
log : main ↪️ [redhat-authentication] REDHAT_AUTH_URL: https://sso.redhat.com/auth/realms/redhat-external/
log : main ↪️ [redhat-authentication] KAS_API_URL: https://api.openshift.com
log : main ↪️ [redhat-authentication] CLIENT_ID: podman-desktop
log : main ↪️ Activating extension (redhat.redhat-authentication) with max activation time of 20 seconds
log : main ↪️ [redhat-authentication] starting redhat-authentication extension
log : main ↪️ Activating extension (redhat.redhat-authentication) ended in 45 milliseconds
log : main ↪️ Activating extension (redhat.openshift-local) with max activation time of 20 seconds
log : main ↪️ Activating extension (redhat.openshift-local) ended in 12 milliseconds
log : main ↪️ Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.
log : main ↪️ Activating extension (redhat.bootc) with max activation time of 20 seconds
log : main ↪️ [bootc] starting bootc extension
error : main ↪️ [ai-lab] Something went wrong while scanning cache. Error: ENOENT: no such file or directory, stat '/home/mbocek/.var/app/io.podman_desktop.PodmanDesktop/cache/huggingface/hub'
log : main ↪️ [kind] kind extension is active
log : main ↪️ Activating extension (redhat.bootc) ended in 403 milliseconds
log : main ↪️ Activating extension (redhat.openshift-checker) with max activation time of 20 seconds
log : main ↪️ Activating extension (redhat.openshift-checker) ended in 1 milliseconds
log : main ↪️ Activating extension (redhat.redhat-sandbox) with max activation time of 20 seconds
log : main ↪️ [redhat-sandbox] starting extension redhat-developer-sandbox
log : main ↪️ [redhat-sandbox] Config file location /home/mbocek/.kube/config
log : main ↪️ Activating extension (redhat.redhat-sandbox) ended in 8 milliseconds
log : main ↪️ PluginSystem: initialization done.
log : main ↪️ Skipping update for extension redhat.ai-lab because installed version 1.7.2 is greater or equal to latest available version 1.7.2
log : main ↪️ Skipping update for extension redhat.redhat-authentication because installed version 1.0.6 is greater or equal to latest available version 1.0.6
log : main ↪️ Skipping update for extension redhat.openshift-local because installed version 2.0.0 is greater or equal to latest available version 2.0.0
log : main ↪️ Skipping update for extension redhat.bootc because installed version 1.9.1 is greater or equal to latest available version 1.9.1
log : main ↪️ Skipping update for extension redhat.openshift-checker because installed version 0.1.5 is greater or equal to latest available version 0.1.5
log : main ↪️ Skipping update for extension redhat.redhat-pack because installed version 1.0.1 is greater or equal to latest available version 1.0.1
log : main ↪️ Skipping update for extension redhat.redhat-sandbox because installed version 0.0.5 is greater or equal to latest available version 0.0.5
error : main ↪️ [bootc] Command execution failed with exit code 1: Command execution failed with exit code 1
log : main ↪️ [kind] kind extension is active
log : main ↪️ [kind] kind extension is active
error : main ↪️ [bootc] Command execution failed with exit code 1: Command execution failed with exit code 1
error : main ↪️ [bootc] Command execution failed with exit code 1: Command execution failed with exit code 1
error : main ↪️ [bootc] Command execution failed with exit code 1: Command execution failed with exit code 1
error : main ↪️ [bootc] Command execution failed with exit code 1: Command execution failed with exit code 1
@HunterGerlach @bocekm Hello, thank you for your report and feedback. I tried to reproduce the issue but couldn’t. Could you please try refreshing the catalog on the Authentication page and check the developer console logs? That should help us understand what’s causing the issue. The error message should be in the following format: Unable to fetch the available extensions: ${String(requestErr.message)}.
@amisskii, I've just done that and all that got added to the log was:
main ↪️ Fetched https://registry.podman-desktop.io/api/extensions.json in 337.97494699999515ms
main ↪️ [bootc] Command execution failed with exit code 1: Command execution failed with exit code 1
Is there a way to switch on more verbose logging?
@amisskii, I've just done that and all that got added to the log was:
main ↪️ Fetched https://registry.podman-desktop.io/api/extensions.json in 337.97494699999515ms main ↪️ [bootc] Command execution failed with exit code 1: Command execution failed with exit code 1Is there a way to switch on more verbose logging?
Thank you for your response. I'm afraid not. My suspicion was that it couldn't fetch data from the catalog for some reason, but it looks like the fetching is working fine, so the problem must be elsewhere.