After installing 1.6.0 I am unable to access any logs

[AmiSMB]

Actual Behavior

When I check the logs of a container inside a running pod I do not see any logs. Reverted back to 1.5.1 and I can see the logs again.

Steps to Reproduce

Install or upgrade to Rancher Desktop 1.6.0 and check the logs of any running pod.

Result

No errors are shown and the logs window is just blank

Expected Behavior

Expected the logs window to have logs inside.

Additional Information

No response

Rancher Desktop Version

1.6.0

Rancher Desktop K8s Version

1.24.6

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 10 Pro Version 10.0.19044 Build 19044

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

No response

Windows User Only

N/A

[gunamata]

I could view the pods and logs for a sample app deployment.. @AmiSMB , Do you mind sharing the steps you followed please?

Here are the steps I followed.

helm repo add bitnami https://charts.bitnami.com/bitnami
 
helm install --wait --timeout=20m wordpress bitnami/wordpress --set=service.type=NodePort --set=volumePermissions.enabled=true --set=mariadb.volumePermissions.enabled=true

Once the pods came up, I opened the Dashboard and could see the pods, and view logs..

[fiburonsk]

I see similar behavior in windows 10 starting with rancher desktop 1.6.0, 1.6.1, and 1.6.2. I'm using Containerd instead of Moby and I've seen this on kubernetes versions 1.25.2 and 1.25.3.

I can consistently reproduce this if I have the dashboard open and import yaml or run a kubectl apply, typically i'm importing a deployment. Then I select execute shell on the deployment page or use execute shell or show logs from the pods page for the newly imported deployment or pods. Instead of a green "Connected" message I get a red "Disconnected" message for the status and if it is a shell it never connects or if it is a log then it remains empty. This is only for newly imported configurations. Any deployments and pods that were already running when I opened the dashboard I can still shell into and view logs for.

In verifying this I've also just learned that if I scale a service that I can view logs / shell into down to 0 and then scale it back to 1 I get the same disconnected status on that pod.

I've found that closing the dashboard and then reopening it through the systray icon restores the capability and then I can shell and view logs.

[fiburonsk]

I've installed rancher desktop 1.7.0 and I am still seeing the same behavior when trying to view logs or execute shell after importing a deployment or redeploying an existing deployment.
If i redeploy my adminer deployment and then do execute shell once it is ready I get the first image and a similar view when going to the pod and selecting view logs (2nd image). When I close the dashboard and reopen it through the systray icon then executing shell and viewing logs works as expected.

execute shell:

view logs:

After closing the dashboard and reopening it this is what i get now when i try and view logs.

Now instead of a status of disconnected the status shows connected.

[vitorpmoreira]

Can confirm this happens to me too, since 1.6.0. The dashboard must be closed and re-opened to be able to access the logs for new pods. This is actually very annoying. I've been using a new instance of Rancher or the Kubernetes Dashboard because this bug makes it kinda unusable.

[gunamata]

I could reproduce the issue with below steps.

• Start Rancher Desktop
• Open Cluster Explorer Dashboard. Switch to Workloads > Pods page.
• Run the below commands in a terminal.

helm repo add bitnami https://charts.bitnami.com/bitnami`
helm install --wait --timeout=20m wordpress bitnami/wordpress --set=service.type=NodePort --set=volumePermissions.enabled=true --set=mariadb.volumePermissions.enabled=true

• Wait for the pods to appear and reach Running state.
• View pod logs. You will not see log messages.
• Close the Cluster Explorer Dashboard and reopen
• Go to Workloads > Pods page and view logs. You will see log messages this time.

[gtjarks]

it's the same for me. Rancher Desktop Version: 1.8.1 K8s Version: v1.26.3 Operating System / Build Version: Windows 10 Pro Version 22H2 Build 19045.2788

[prayagsingh]

Still same. Is anyone able to fix it? Rancher Desktop Version: 1.8.1 K8s Version: v1.26.4 Operating System / Build Version: Windows 10 Pro Version 22H2

[ZL7573]

Still seeing this with 1.9.0-tech-preview on windows and mac

[jiafangtao]

FYI. I see this issue with Rancher Desktop 1.10.0, on Windows 11 home edition. If you need more details, please let me know.

[RaqieT]

I could reproduce the issue with below steps.

• Start Rancher Desktop
• Open Cluster Explorer Dashboard. Switch to Workloads > Pods page.
• Run the below commands in a terminal.

helm repo add bitnami https://charts.bitnami.com/bitnami`
helm install --wait --timeout=20m wordpress bitnami/wordpress --set=service.type=NodePort --set=volumePermissions.enabled=true --set=mariadb.volumePermissions.enabled=true

• Wait for the pods to appear and reach Running state.
• View pod logs. You will not see log messages.
• Close the Cluster Explorer Dashboard and reopen
• Go to Workloads > Pods page and view logs. You will see log messages this time.

Same thing on Fedora 38. Rancher Desktop 1.10.0 (AppImage).

[gaktive]

We need to get the Rancher shell integration in to resolve this, so pushing this out of a milestone since we're blocked. #2822 is that epic.