Code change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: N/A (remote extensions are needed) <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.81.0 (Universal) and 1.82.0-insider (Universal) OS Version: MacOS 13.3.1 (22E261) [Ventura] Steps to Reproduce: a repository with a devcontainer from GitHub Codespaces (either in browser VS Code, or desktop) at the Source Control tab - it says "Scanning folder for git repositories…" I have seen this issues before months back, and it was fixed in Insiders and subsequently the release version - but it is back again and very frustrating. I have a minimal repo here - you will need to create a Codespace to see the issue (or choose a different devcontainer workflow). The issue could be to do with the docker image used, I think last time there was some suggestion of a problem with Alpine (or Alpine containers), and I believe the Jekyll container is based on Alpine. too.
it looks like has resurfaced. I am able to reproduce with the latest Insiders release.
Very likely candidate , will investigate tomorrow.
Steps for verification: Reopen in a container Verify server launches and integrated terminal works fine
I've checked in the latest Insiders release and the same bug seems to still be present when using GitHub Codespaces (both in web version of VS Code insiders, and desktop version of VS Code insiders when connecting to the Codespace) Version: 1.83.0-insider (Universal) Commit: Date: 2023-09-13T05:34:48.836Z Electron: 25.8.0 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: Darwin x64 22.4.0
the alpine servers run fine with the provided container configuration, however the git scm is hanging for a different reason can you please look into it
I have created a new Codespace on the linked repository and I am still able to reproduce the problem. As far as I can tell the extension how is completely busted as running "Show Running Extensions" is empty. In the Window output log I see the following: If I look at the Git extension I see the following: !
Ah missed the logs, is based on whereas our server alpine modules are built on . We don't plan to revert the alpine version as is reaching EOL I am closing this as designed, please update the jekyll container to use

Related discussion:
text: { "name": "code-oss-dev", "version": "1.82.0", <del> "distro": "49cc0fbc0a8e222bcce2a7c3bf62e0d23f20d258", </del> <ins> "distro": "2100ad274ed566f978bb917f327b3d99f95d59f2", </ins> "author": { "name": "Microsoft Corporation" },