Unable to access logs or terminal on Linux via WSL

[nicusorflorin]

Describe the bug
I receive the errors:

[9753:0409/131214.162795:ERROR:context_group.cc(184)] ContextResult::kFatalFailure: ES3 is blocklisted/disabled/unsupported by driver.
[9753:0409/131214.193109:ERROR:gl_utils.cc(315)] [GroupMarkerNotSet(crbug.com/242999)!:B8A8F303B8010000] GL_INVALID_ENUM: Invalid pname.
[9753:0409/131214.193352:ERROR:gl_utils.cc(315)] [GroupMarkerNotSet(crbug.com/242999)!:B8A8F303B8010000] GL_INVALID_ENUM: Invalid pname.

I run the kui-linux-x64 build on Ubuntu 20 installed on wsl on windows 11. When i try to access

Steps to reproduce the behavior

1. Download kui-linux-x64 build on Ubuntu 20 installed on wsl on windows 11
2. Unzip and add it to the path
3. Launch and run kubectl get pods
4. Select a pod and click on Logs or Terminal
5. Receive above mentioned error

Expected behavior
Should open the logs or the terminal

System

• Kui version: 13.1.4
• Operating system: Windows 11 -> WSL -> Ubuntu 20.04

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.