search

microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
164.99k stars 29.54k forks source link

Extensions not installing on vscode insiders when running inside a dev container #175705

Open kurt-mueller-osumc opened 1 year ago

kurt-mueller-osumc commented 1 year ago

Does this issue occur when all extensions are disabled?: n/a

n/a I think. The code editor cannot install extensions when booting up a development container. I've ran the 'Help: Start Extension Bisect' command to reload the container without any extensions installed.... unfortunately, when I attempt to install the ms-python.python extension, the extension is stuck on 'Installing'.

Version: 1.76.0-insider Commit: 92da9481c0904c6adfe372c12da3b7748d74bdcb Date: 2023-02-28T11:50:50.947Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Darwin arm64 22.3.0 Sandboxed: Yes

Notes:

I'm on an macos and am using rosetta to emulate x86_64 architecture.

sandy081 commented 1 year ago

Can you please share the following log while you reproduce the issue?

twanwv commented 1 year ago

Logging in 1.76.0

2023-03-02 15:31:50.298 [info] 

2023-03-02 15:31:50.358 [info] Extension host agent started.
2023-03-02 15:31:50.392 [debug] Removing uninstalled extensions: []
2023-03-02 15:31:50.495 [info] [127.0.0.1][eafae52d][ManagementConnection] New connection established.
2023-03-02 15:31:50.676 [info] [127.0.0.1][b5ea7270][ExtensionHostConnection] New connection established.
2023-03-02 15:31:50.703 [info] [127.0.0.1][b5ea7270][ExtensionHostConnection] <209> Launched Extension Host Process.
2023-03-02 15:32:24.559 [info] [127.0.0.1][eafae52d][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
2023-03-02 15:32:24.623 [info] [127.0.0.1][b5ea7270][ExtensionHostConnection] <209> Extension Host Process exited with code: 0, signal: null.
2023-03-02 15:32:27.697 [info] [127.0.0.1][c7784cbf][ManagementConnection] New connection established.
2023-03-02 15:32:28.398 [info] [127.0.0.1][8d893acd][ExtensionHostConnection] New connection established.
2023-03-02 15:32:28.406 [info] [127.0.0.1][8d893acd][ExtensionHostConnection] <797> Launched Extension Host Process.

Logging in 1.75.1

2023-03-02 15:33:52.356 [info] 

2023-03-02 15:33:52.406 [info] Extension host agent started.
2023-03-02 15:33:52.514 [info] [127.0.0.1][36eba529][ManagementConnection] New connection established.
2023-03-02 15:33:52.516 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:52.576 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:52.622 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:52.655 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:52.793 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:52.798 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:52.806 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:52.808 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:52.810 [info] [127.0.0.1][147a00d1][ExtensionHostConnection] New connection established.
2023-03-02 15:33:52.823 [info] [127.0.0.1][147a00d1][ExtensionHostConnection] <236> Launched Extension Host Process.
2023-03-02 15:33:52.858 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:52.873 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:52.880 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:52.886 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:52.935 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:53.139 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:53.237 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:53.241 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:53.242 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:53.243 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:53.257 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:53.263 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:53.267 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:53.269 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:54.305 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:54.314 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.
2023-03-02 15:33:59.435 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.15]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0-insider.
2023-03-02 15:33:59.439 [error] [/root/.vscode-server/extensions/ms-toolsai.jupyter-2023.2.1000592019]: Extension is not compatible with Code 1.75.1. Extension requires: ^1.76.0.

Note: all desired extensions are installed inside the container on 1.75.1

kurt-mueller-osumc commented 1 year ago

Hi Sandeep,

There is no option to View Remote Server but I do have the ability to View Server. I've taken a screenshot of the command I ran:

Screenshot 2023-03-02 at 10 30 52 AM

It gave me the following output:

2023-03-02 15:29:03.775 [info] 

2023-03-02 15:29:03.879 [info] Extension host agent started.
2023-03-02 15:29:03.997 [debug] Removing uninstalled extensions: []
2023-03-02 15:29:05.651 [info] [127.0.0.1][980f0093][ManagementConnection] New connection established.
2023-03-02 15:29:06.440 [info] [127.0.0.1][bab05b13][ExtensionHostConnection] New connection established.
2023-03-02 15:29:06.474 [info] [127.0.0.1][bab05b13][ExtensionHostConnection] <609> Launched Extension Host Process.

Let me know if you need any additional info.

kurt-mueller-osumc commented 1 year ago

I think extensions fail to install on containers that emulate x86 architecture using Rosetta virtualization. I've been able to install extensions in containers that are aarch based.

sandy081 commented 1 year ago

I do not see any installation related entries in the logs. May I know how are you installing the extension? Are you triggering this from extensions UI? Can you also please enable log level to trace F1 > Set Log Level... > Trace and reproduce the issue?

sandy081 commented 1 year ago

@chrmarti It seems this is specific to containers that emulate x86 architecture using Rosetta virtualization - does it rings any bells?

kurt-mueller-osumc commented 1 year ago

@sandy081 When I set the log levels to "trace", I can see a PackageIsUnreadable exception being thrown when I attempt to install extensions (via vscode's extension ui):

[45916 ms] [15:54:20] Extension signature verification details for ms-toolsai.jupyter-renderers 1.0.15:
Package file size:  82
Signature archive file size:  11100
Manifest file size:  6076
Signature file size:  11986
Manifest file hash:  iNySwbbf5cnq+zEvmBtV3PPIo/Zw518d02NsfAKeoZQ=
Signature file hash:  gG/0OxuEf7CddE+i89TBtc0oXH7DR2lNo2V9hwI/G7A=
System.IO.FileNotFoundException: IO_FileNotFound_FileName, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.jupyter-renderers-1.0.15
IO_FileName_Name, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.jupyter-renderers-1.0.15
   at Interop.ThrowExceptionForIoErrno(ErrorInfo, String, Boolean)
   at Interop.CheckIo(Error, String , Boolean )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, OpenFlags, Int32, Func`4)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, UnixFileMode, Int64& , UnixFileMode& , Func`4 )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1 , Func`4 )
   at System.IO.Strategies.OSFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.UnixFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream, String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64, Nullable`1)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, Boolean)
   at System.IO.FileInfo.OpenRead()
   at Microsoft.VisualStudio.Extensions.Signing.ExtensionPackage.OpenRead(FileInfo)
   at Microsoft.VisualStudio.Extensions.Signing.CLI.Program.VerifyAsync(FileInfo, FileInfo, FileInfo, FileInfo, Func`2, Boolean, Boolean)
Exit code:  PackageIsUnreadable

[45927 ms] [15:54:20] Extension signature verification details for ms-toolsai.jupyter-keymap 1.1.0:
Package file size:  78
Signature archive file size:  9554
Manifest file size:  1266
Signature file size:  11977
Manifest file hash:  XLhYoMpV96SN8l4cK7gR2SGGczuL3n+zsMNkEZGS3So=
Signature file hash:  h7qtOCYh5W21g6iWYrAf8DCNIBGYtg5kBPbUZzm08n8=
System.IO.FileNotFoundException: IO_FileNotFound_FileName, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.jupyter-keymap-1.1.0
IO_FileName_Name, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.jupyter-keymap-1.1.0
   at Interop.ThrowExceptionForIoErrno(ErrorInfo, String, Boolean)
   at Interop.CheckIo(Error, String , Boolean )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, OpenFlags, Int32, Func`4)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, UnixFileMode, Int64& , UnixFileMode& , Func`4 )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1 , Func`4 )
   at System.IO.Strategies.OSFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.UnixFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream, String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64, Nullable`1)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, Boolean)
   at System.IO.FileInfo.OpenRead()
   at Microsoft.VisualStudio.Extensions.Signing.ExtensionPackage.OpenRead(FileInfo)
   at Microsoft.VisualStudio.Extensions.Signing.CLI.Program.VerifyAsync(FileInfo, FileInfo, FileInfo, FileInfo, Func`2, Boolean, Boolean)
Exit code:  PackageIsUnreadable

[45942 ms] [15:54:20] Extension signature verification details for ms-toolsai.vscode-jupyter-slideshow 0.1.5:
Package file size:  88
Signature archive file size:  10219
Manifest file size:  2789
Signature file size:  11978
Manifest file hash:  AqePx/Jq+/h0mm3d80rh1MJSKc78Xq3ERcVCC+CDPhQ=
Signature file hash:  yglIqMdlccgWMean0TXtRRiD+5RejR1LWNkR7gWAIZA=
System.IO.FileNotFoundException: IO_FileNotFound_FileName, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.vscode-jupyter-slideshow-0.1.5
IO_FileName_Name, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.vscode-jupyter-slideshow-0.1.5
   at Interop.ThrowExceptionForIoErrno(ErrorInfo, String, Boolean)
   at Interop.CheckIo(Error, String , Boolean )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, OpenFlags, Int32, Func`4)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, UnixFileMode, Int64& , UnixFileMode& , Func`4 )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1 , Func`4 )
   at System.IO.Strategies.OSFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.UnixFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream, String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64, Nullable`1)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, Boolean)
   at System.IO.FileInfo.OpenRead()
   at Microsoft.VisualStudio.Extensions.Signing.ExtensionPackage.OpenRead(FileInfo)
   at Microsoft.VisualStudio.Extensions.Signing.CLI.Program.VerifyAsync(FileInfo, FileInfo, FileInfo, FileInfo, Func`2, Boolean, Boolean)
Exit code:  PackageIsUnreadable

[45984 ms] [15:54:20] Extension signature verification details for ms-toolsai.jupyter 2023.2.1000592019:
Package file size:  83
Signature archive file size:  17353
Manifest file size:  24441
Signature file size:  12017
Manifest file hash:  16dnVUBrhyTjSMrCk1/ZR8Tdb/pfNoJ+F19PWP5MU5Y=
Signature file hash:  EudiXyv1VScg+MtaveqbbAos/OP8bOnscTngAdYU67E=
System.IO.FileNotFoundException: IO_FileNotFound_FileName, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.jupyter-2023.2.1000592019
IO_FileName_Name, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.jupyter-2023.2.1000592019
   at Interop.ThrowExceptionForIoErrno(ErrorInfo, String, Boolean)
   at Interop.CheckIo(Error, String , Boolean )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, OpenFlags, Int32, Func`4)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, UnixFileMode, Int64& , UnixFileMode& , Func`4 )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1 , Func`4 )
   at System.IO.Strategies.OSFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.UnixFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream, String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64, Nullable`1)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, Boolean)
   at System.IO.FileInfo.OpenRead()
   at Microsoft.VisualStudio.Extensions.Signing.ExtensionPackage.OpenRead(FileInfo)
   at Microsoft.VisualStudio.Extensions.Signing.CLI.Program.VerifyAsync(FileInfo, FileInfo, FileInfo, FileInfo, Func`2, Boolean, Boolean)
Exit code:  PackageIsUnreadable

[45994 ms] [15:54:20] Extension signature verification details for ms-toolsai.vscode-jupyter-cell-tags 0.1.6:
Package file size:  88
Signature archive file size:  10628
Manifest file size:  3690
Signature file size:  12019
Manifest file hash:  unCeiJeg1jTT/MymV3D5FyXMnKJ6elXaKo1BLh3j9wo=
Signature file hash:  5UaTECA1TDNT/YomULDUHqrCXIpItcO0DDVFKhekV2A=
System.IO.FileNotFoundException: IO_FileNotFound_FileName, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.vscode-jupyter-cell-tags-0.1.6
IO_FileName_Name, /home/.vscode-server-insiders/extensionsCache/ms-toolsai.vscode-jupyter-cell-tags-0.1.6
   at Interop.ThrowExceptionForIoErrno(ErrorInfo, String, Boolean)
   at Interop.CheckIo(Error, String , Boolean )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, OpenFlags, Int32, Func`4)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, UnixFileMode, Int64& , UnixFileMode& , Func`4 )
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1 , Func`4 )
   at System.IO.Strategies.OSFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.UnixFileStreamStrategy..ctor(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String, FileMode, FileAccess, FileShare, FileOptions, Int64, Nullable`1)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream, String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64, Nullable`1)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions, Int64)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, FileOptions)
   at System.IO.FileStream..ctor(String, FileMode, FileAccess, FileShare, Int32, Boolean)
   at System.IO.FileInfo.OpenRead()
   at Microsoft.VisualStudio.Extensions.Signing.ExtensionPackage.OpenRead(FileInfo)
   at Microsoft.VisualStudio.Extensions.Signing.CLI.Program.VerifyAsync(FileInfo, FileInfo, FileInfo, FileInfo, Func`2, Boolean, Boolean)
Exit code:  PackageIsUnreadable

[77751 ms] [IPC Library: Pty Host] TRACE ptyService#setLayoutInfo [ { isActive: true, activePersistentProcessId: 0, terminals: [] } ]
sandy081 commented 1 year ago

Seems extension signing verification related.

CC @isidorn / @dtivel

chrmarti commented 1 year ago

@chrmarti It seems this is specific to containers that emulate x86 architecture using Rosetta virtualization - does it rings any bells?

No, I tried to reproduce and for me extension installation seems to hang for some extensions when using the following config on a M1 mac:

{
    "image": "amd64/ubuntu",
    "customizations": {
        "vscode": {
            "extensions": [
                "ms-python.python"
            ]
        }
    }
}

So maybe this is not the same issue.

image
RLC92 commented 1 year ago

I am also experiencing this issue.

Attempting to manually install in the container sometimes fixes the extensions but for some extensions - seemingly chosen at random - you'll get PackageIsUnreadable errors preventing installation.

Version: 1.76.2 (user setup)
Commit: ee2b180d582a7f601fa6ecfdad8d9fd269ab1884
Date: 2023-03-14T17:55:54.936Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No
kf6kjg commented 1 year ago

Since https://github.com/microsoft/vscode-remote-release/issues/8169 has been closed as a duplicate of this issue, I figured that I should note here that the closed issue has a lot of commentary and debugging of this issue.

1995parham commented 11 months ago

I don't have this issue using Insider version on M2Pro, but after upgrading macOS and Insider I have this issue and disable the plugin verification resolved the issue for now.

sandy081 commented 10 months ago

Can you (those who subscribed) please verify if this issue still exists?

mdrakiburrahman commented 10 months ago

@sandy081 - I just reprod it 2 days ago. But my version of VSCode might not be the version you've pushed the fix to.

This workaround unblocked our team: image

Could you let me know what to try:

  1. Which VSCode, regular, or insiders
  2. Which version of VSCode to install to test the fix
sandy081 commented 10 months ago

@mdrakiburrahman Thanks for reaching out. It would be great if you can update to latest stable and try. Can you please let us know with which extension you are having this issue? Can you please share your platform and following log while you reproduce

mdrakiburrahman commented 10 months ago

Hi @sandy081,

Looks like it's working now - I might have just received the update last night!

image

The way I noticed this one my daily used extensions, Metals no longer installed in our devcontainer.

It's now installing fine:

image

Thank you!

ragheb-deriv commented 10 months ago

I just reported the same issue here : https://github.com/microsoft/vscode-remote-release/issues/9525

Wesztman commented 10 months ago

I can also confirm that I had problems with extensions not installing in stable

image

But with insiders it is now working :)

image

EDIT: Apparently not working... Now when I started VSCode this morning it had installed old extensions in my devcontainer... Extensions which I had in my devcontainer.json several days ago..

humphd commented 9 months ago

I've just updated to 1.87.0 and it happened to me. None of the extensions listed in my .devcontainer/devcontainer.json are installed now. ~I tried the suggestion in https://github.com/microsoft/vscode/issues/175705#issuecomment-1906509931, but it didn't have any effect.~ I was actually able to set "extensions.verifySignature": false under settings: {...} in my devcontainer.json and get them to load.

Screenshot 2024-03-05 at 3 22 06 PM

Version: 1.87.0 (Universal) Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2 Date: 2024-02-27T23:42:56.944Z Electron: 27.3.2 ElectronBuildId: 26836302 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Darwin arm64 23.2.0

trollspank commented 9 months ago

Having the exact same issue on Mac M1 as well, I've also tried installing the non-M1 version of VSCode, same issue. Wiped all my extensions, restarted, nothing (except errors trying to start my devcontainer w/o the docker extension of course)

mdrakiburrahman commented 8 months ago

Hi @sandy081

Bad news - this broke again on 1.87.1:

image

Workaround was to revert back "extensions.verifySignature": false again.

Is there regression tests setup for whoever is making these commits to break extensions?

papakpmartin commented 8 months ago

I'm also seeing this problem. Apple M2, running 13.3.1 (22E261).

customizations.vscode.settings.extensions.verifySignature: false allows things to work.

Version: 1.87.2 (Universal) Commit: 863d2581ecda6849923a2118d93a088b0745d9d6 Date: 2024-03-08T15:21:31.043Z (6 days ago) Electron: 27.3.2 ElectronBuildId: 26836302 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Darwin arm64 22.4.0

DanseMacabre commented 7 months ago

Is there any update on this? For reference to anyone else checking this thread, "extensions.verifySignature": false can also go in the Remote Settings JSON file (.vscode-server/data/Machine/settings.json) if you attach to an existing container rather than one created by a devcontainer.json, and if your container is destroyed and re-built from scratch, you may need to re-add this line to the file as it exists on the container and will also be destroyed.

j-bennet commented 6 months ago

+1, Python extension, even with "extensions.verifySignature": false.

bo-values commented 6 months ago

My workaround is here.

MacBook Air M2 macOS Venture 13.2.1 Visual Studio Code 1.89.0 (Universal) DevContainers v0.362.0 Debian OS

## Dockerfile
FROM --platform=linux/amd64 mcr.microsoft.com/vscode/devcontainers/base:dev-bullseye
  1. set "extensions.verifySignature": false at devcontainer.json
  2. build container > I faced extensions is stuck on 'Installing'.
  3. then, click cloud button at extensions panel like image. some extensions were installed,but not perfect.
  4. click Rebuild Container.
  5. all extensions was installed!

image image

coffepowered commented 6 months ago

Experiencing the same issue on M1 pro: extensions don't install on the Remote Container

Host:

My tests:

DanseMacabre commented 6 months ago

Experiencing the same issue on M1 pro: extensions don't install on the Remote Container

Host:

  • osx 14.1.1

  • vscode 1.89.1 arm64 via homebrew (briefly tried previous version as well)

  • no devcontainer.json, just attaching to a container in docker-compose

My tests:

  • Extensions install locally

  • Extension install in attached container if I don't specify platform

  • ms-python extension does NOT install in attached container if I build using platform: linux/amd64 (tried "extensions.verifySignature": false in .vscode/settings.json with no luck)

Try following the workaround in my previous comment:

Add the line to the remote workspace json file. You may need to restart the container or kill the hung vscode process(es) that are in the container to have this change take effect.

mindplay-dk commented 3 weeks ago

I'm on Win 11 using WSL2 with Docker, stable VS Code 1.95.2 - no extensions get installed.

I get this warning for any extensions listed in my devcontainer.json:

This extension is disabled in this workspace because it is defined to run in the Remote Extension Host. Please install the extension in 'Dev Container: chillproductions.com' to enable

Image

I have to install the extensions again every time I open this project.

It sounds like some users have been able to work around this adding "extensions.verifySignature": false to customizations.vscode.extensions - this did not work for me.

Rebuilding the container, no difference.

Is there a recommended workaround? Should I move the extensions to suggestions instead? That way at least when someone else checks out the project, they can see which extensions were supposed to be installed.

If it matters, my Dockerfile derives from mcr.microsoft.com/devcontainers/php:8.3.

Let me know if there's anything I can test or provide?