`Common OS utilities` in `Node.js & TypeScript` is buggy

[Zwyx]

Issue Type: Bug

Hi all and thanks for making VS Code :-)

I've noticed a strange behaviour when trying to use the Common OS utilities after choosing the Node.js & TypeScript definition to create a development container:

Steps to reproduce:

• Open any folder on your machine
• Ctrl+Shift+P
• Remote-Containers: Reopen in Container
• Select Node.js & TypeScript
• Select 16-bullseye
• Select Common OS utilities and click OK

Expected: the container creation process starts.

Actual: either nothing happens, or the following message appears in a dialog:

Command 'Remote-Containers: Reopen in Container' resulted in an error (Can not delete in empty document)

I've also noticed that if I select other entries (Docker-in-Docker, Git, Lightweight desktop, SSH) among Common OS utilities, then the container creation process sometime starts, but I can't see no trace of these "Common OS utilities" in the devcontainer.json file. Which, I believe, confirm that there is an issue with Common OS utilities.

Edit: here's a recording showing the bug:

• I first try to select Common OS utilities → the creation process doesn't start
• I then deselect it and select Git → again, the creation process doesn't start
• I then restart from scratch and select Git only → now it works, the container gets created

Cheers

VS Code version: Code 1.62.2 (3a6960b964327f0e3882ce18fcebd07ed191b316, 2021-11-11T20:51:30.084Z)
OS version: Linux x64 4.19.0-6-amd64
Restricted Mode: No

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1600)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	1, 2, 2
Memory (System)	7.52GB (0.83GB free)
Process Argv	--no-sandbox --unity-launch --crash-reporter-id 8427d3c3-a0db-4b7a-b8a9-089b1682613d
Screen Reader	no
VM	0%
DESKTOP_SESSION	lightdm-xsession
XDG_CURRENT_DESKTOP	XFCE
XDG_SESSION_DESKTOP	lightdm-xsession
XDG_SESSION_TYPE	x11

Extensions (13)

Extension	Author (truncated)	Version
history-in-sublime-merge	adh	1.2.14
vscode-eslint	dba	2.2.2
prettier-vscode	esb	9.0.0
codespaces	Git	1.3.6
vscode-pull-request-github	Git	0.32.0
observable-js	Gor	0.4.14
templex	hiv	1.1.0
remote-containers	ms-	0.205.2
remote-ssh	ms-	0.66.1
remote-ssh-edit	ms-	0.66.1
vscode-remote-extensionpack	ms-	0.21.0
vscode-typescript-tslint-plugin	ms-	1.3.3
code-spell-checker	str	2.0.12

(1 theme extensions excluded)

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30384386
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsqsis300:30386381
vsaa593cf:30376535
vssld246:30401890
vscexrecpromptc:30400060

[joeriddles]

I am also experiencing this when trying to set up a dev container for Jekyll.

[DanielRuf]

Same for the default GitHub codespace image.

[Chuxel]

This was a bug in the insiders edition of the extension and that shouldn't have been appearing at all because it's already been run in those definitions. The reason you didn't see anything, is it was skipped because of it. #5990 and #6069 are related with #5990 being the reason for the error.

You should no longer see it listed in the latest version of the Remote - Containers extension, so closing as dupe of the other two for remaining issues.