Recommended workspace extensions are not prompted after dev container is recreated #186867
Labels
bug
Issue identified by VS Code Team member as probable bug
extension-recommendations
Extension recommendations issues
extensions
Issues concerning extensions
insiders-released
Patch has been released in VS Code Insiders
verified
Verification succeeded
Milestone
Type: Bug
We use docker containers (of our own) and using "Attach to a running container" feature of dev containers, we get connected to these in VS Code.
In a remote folder in container, we have a .vscode folder with recommended extensions. This works quite well, but only the first time.
When the remote workspace is opened which contains the recommended extensions settings, it will ask and install them when accepted.
However, if the containers are recreated after this, it will no longer ask to install recommended extensions. And since the containers are recreated, the extensions which were previously installed into the container are all gone.
The only way I could find to make VSCode to ask avbout the recommended extensions again is by going to the host computer and removing .config/Code folder. Once I do that and connect to the recreated container again, I will get the recommendations question.
It would be great to be able to avoid this. I'm not sure if it is a bug or just a missing feature. I think this should be considered a bug.
VS Code version: Code 1.79.2 (695af09, 2023-06-14T08:59:55.818Z)
OS version: Linux x64 6.4.0-gentoo
Modes:
Remote OS version: Linux x64 6.4.0-gentoo
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Extensions (20)
A/B Experiments
The text was updated successfully, but these errors were encountered: