The containers running wslc cannot be displayed

[m178520]

1.I work in the field of robotics, and many scenarios require visual display. I tried to run a container using wslc and executed xclock in the container environment, but it prompted that the display could not be made
2.Containers running in wslc cannot be attached to vscode

1.Can wslg in wsl2 also be used in containers where wslc runs to enable visual display as well
2.Add image and container management in the VScode plugin wsl, and it can be attached to VScode for operation

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[m178520]

/feature

[github-actions]

Diagnostic information

Found '/feature', adding tag 'feature'

[chemwolf6922]

Hi @m178520 .
For 1. You can use the normal X forwarding method to show gui with wlsc:

1. Install a x server on windows. For example, vcxsrv.
2. Set the Display env when creating the container with the option: -e DISPLAY="${hostIp}:0". Please note that you need to use a host ip that's other than the public one. As that's mirrored inside the VM and will block the traffic. For example, you can use the host ip on the Ethernet adapter vEthernet (WSL (Hyper-V firewall)) interface.

For 2. I'm not sure if this meets your requirements. VS Code dev containers will soon have a release with wslc support. You may find more details here: https://devblogs.microsoft.com/commandline/wsl-container-is-now-available-for-public-preview/#vs-code-dev-containers