Remote-Containers commands do not receive selection objects from remote Docker extension

[ucheNkadiCode]

• VSCode Version: 1.52.1
• Local OS Version:
• Remote OS Version:
• Remote Extension/Connection: Docker + WSL 2

Steps to Reproduce:
Adding @paulyuk for repro steps

1. From the Docker Extension, on the Volumes tab, when selecting a volume to Inspect in VS Code using the Remote Container extension, the Inspect in VS Code command fails.

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: IDK

[chrmarti]

This is microsoft/vscode#111238 which has been closed with no fix.

To summarize: The Docker extension runs on the remote extension host inside WSL while the Remote-Containers extension runs on the local extension host on Windows. In this setup the selection from the Docker viewlet is not passed to the Remote-Containers command.

[chrmarti]

A possible workaround would be to have the Docker extension offer a command to look up the current selection. When the Remote-Containers command is run with no selection passed, it would use that lookup command to get the volume name.

The same issue exists when trying to attach to a container from the Docker viewlet. There we open a container picker when the command does not receive a selection. So the user gets to pick the container twice which is not ideal.

[markgrin]

I experience the same problem. Also I think it is an important problem, because fixing it would enable people to work with kubernetes\minikube in a WFH setting.

[mustanggb]

I have the problem after right clicking on a container and selecting Attach Visual Studio Code instead of attaching it opens another list Select the container to attach VS code and forces the same selection for a second time.

Very annoying.

The two lists aren't even in the same order.