# Codebase Indexing No Longer Working Inside Dev Containers

**URL:** <https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858>\
**Category:** Bug Reports\
**Created:** [September 20, 2024, 6:44pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858 "2024-09-20T18:44:21Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![trevordcampbell](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/trevordcampbell/32/5652_2.png) [@trevordcampbell](https://forum.cursor.com/u/trevordcampbell)\
**Post date:** [September 20, 2024, 6:44pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/1 "2024-09-20T18:44:21Z")

</div>

I do most of my development inside Dev Containers, and largely have not had many issues using Cursor inside Dev Containers.

However I have a new issue where the Codebase Indexing feature no longer works when developing inside of Dev Containers. Previously, this feature functioned normally / as expected when developing both locally as well as inside of Dev Containers.

Now, when I launch a project inside a Dev Container, the Codebase Indexing feature hangs on “_Loading…_” indefinitely, and the button / option to begin or initiate indexing never appears:

 ![image](https://us1.discourse-cdn.com/cursor1/original/2X/5/5f9917416d48ee16edd4cf42e63d5145e7aaa5bc.png)

Codebase Indexing can never be conducted, as the controls for initiating it never appear (held up by the indefinite “_Loading…_” status)

Using the same project locally, outside of a Dev Container, the Codebase Indexing feature works normally, and the button / option to index appears and functions as expected:

 ![Screenshot 2024-09-20 at 2.35.54 PM](https://us1.discourse-cdn.com/cursor1/original/2X/1/1f4d37f8e93fa7ba3bfa26bd830b1085328cacae.png)

 ![Screenshot 2024-09-20 at 2.36.14 PM](https://us1.discourse-cdn.com/cursor1/original/2X/3/39c5b4cd57f0ccbfde2f348757445af59cdd3bf6.png)

So the issue is certainly isolated to the Codebase Indexing feature not working correctly within Dev Containers.

These are the version details for my current Cursor installation:

```auto
Version: 0.41.1
VSCode Version: 1.91.1
Commit: 10e3716b510a5d447c1a07b2edd37a352bbea4d0
Date: 2024-09-18T07:38:06.522Z (2 days ago)
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 24.0.0

```

However this issue was also noticed with the previous version I had installed as well (an unknown version now, but it was recent within the last week or so)

I also noticed this issue both using Docker Desktop-based containers as well as Orbstack-based containers, so it’s likely not a container / docker issue.

Has anyone else noticed this new issue? Or has anyone been able to determine a fix for it yet?

---

<div class="post-metadata">

**Author:** ![5inGularity](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/5ingularity/32/5950_2.png) [@5inGularity](https://forum.cursor.com/u/5inGularity)\
**Post date:** [September 24, 2024, 8:08am UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/2 "2024-09-24T08:08:13Z")

</div>

I’m also facing this issue

```auto
Version: 0.41.2
VSCode Version: 1.91.1
Commit: 297991d169fa3a11975c5aa95adc69be73250c70
Date: 2024-09-21T04:18:39.370Z (2 days ago)
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.6.0

```

---

<div class="post-metadata">

**Author:** ![netcaster](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/netcaster/32/6215_2.png) [@netcaster](https://forum.cursor.com/u/netcaster)\
**Post date:** [September 24, 2024, 9:07am UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/3 "2024-09-24T09:07:37Z")

</div>

Current version is Not ready for arm system. Which caused codebase indexing keeping loading status and backend File sync process is disabled due to that.

workbench.desktop.main.js:2774 Activating extension ‘anysphere.cursor-retrieval’ failed: Cannot find module ‘@anysphere/file-service-linux-arm64-gnu’

---

<div class="post-metadata">

**Author:** ![netcaster](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/netcaster/32/6215_2.png) [@netcaster](https://forum.cursor.com/u/netcaster)\
**Post date:** [September 25, 2024, 3:54am UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/4 "2024-09-25T03:54:51Z")

</div>

![Screenshot 2024-09-25 124921](https://us1.discourse-cdn.com/cursor1/original/2X/7/7d2f71d3f0a1ed75feb49f80c1160cdfd22ede1a.png)  
Rollback to 0.40.4 and the issue is gone.

---

<div class="post-metadata">

**Author:** ![sant3e](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sant3e/32/6970_2.png) [@sant3e](https://forum.cursor.com/u/sant3e)\
**Post date:** [October 1, 2024, 2:10pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/5 "2024-10-01T14:10:20Z")

</div>

How can i do this on Mac? I wanted to uninstall and install back, but can’t find for dl that version, for mac

---

<div class="post-metadata">

**Author:** ![atur-yo](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/atur-yo/32/6969_2.png) [@atur-yo](https://forum.cursor.com/u/atur-yo)\
**Post date:** [October 1, 2024, 2:42pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/6 "2024-10-01T14:42:00Z")

</div>

Same problem here, how to install older version like 0.40.4 ?

---

<div class="post-metadata">

**Author:** ![maxritter](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/maxritter/32/20633_2.png) [@maxritter](https://forum.cursor.com/u/maxritter)\
**Post date:** [October 3, 2024, 10:48am UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/7 "2024-10-03T10:48:26Z")

</div>

Also having this issue, it’s really annoying and needs to be fixed!

---

<div class="post-metadata">

**Author:** ![ebweinstein](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ebweinstein/32/7229_2.png) [@ebweinstein](https://forum.cursor.com/u/ebweinstein)\
**Post date:** [October 4, 2024, 5:30pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/8 "2024-10-04T17:30:49Z")

</div>

Same issue. Using SSH in a remote environment [Codebase indexing stuck](https://forum.cursor.com/t/codebase-indexing-stuck/20965)

---

<div class="post-metadata">

**Author:** ![qirui-chen-9](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/qirui-chen-9/32/7046_2.png) [@qirui-chen-9](https://forum.cursor.com/u/qirui-chen-9)\
**Post date:** [October 5, 2024, 4:17am UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/9 "2024-10-05T04:17:37Z")

</div>

[https://dl.todesktop.com/230313mzl4w4u92/versions/0.40.4/mac/dmg/arm64](https://dl.todesktop.com/230313mzl4w4u92/versions/0.40.4/mac/dmg/arm64) that would be awesome!

pname = “cursor”;  
version = “0.41.2”;  
appKey = “230313mzl4w4u92”;  
src = fetchurl {  
url = “[https://dl.todesktop.com/${appKey}/versions/${version}/linux](https://dl.todesktop.com/$%7BappKey%7D/versions/$%7Bversion%7D/linux)”;  
hash = “sha256-zBNNKpSzRKC0R8kscHyCNaMzA/czcYKrAM9vHv2tHsA=”;  
};

---

<div class="post-metadata">

**Author:** ![KyL0N](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kyl0n/32/7378_2.png) [@KyL0N](https://forum.cursor.com/u/KyL0N)\
**Post date:** [October 6, 2024, 1:14pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/10 "2024-10-06T13:14:20Z")

</div>

same here, the remote machine arch is aarch64

```auto
workbench.desktop.main.js:2774 Activating extension 'anysphere.cursor-retrieval' failed: Cannot find module '@anysphere/file-service-linux-arm64-gnu'
Require stack:
- /home/jetson/.cursor-server/cli/servers/Stable-51c8aff7cb5a89f4a0e462fbacab938bdbfaf140/server/extensions/cursor-retrieval/node_modules/@anysphere/file-service/index.js
- /home/jetson/.cursor-server/cli/servers/Stable-51c8aff7cb5a89f4a0e462fbacab938bdbfaf140/server/extensions/cursor-retrieval/dist/main.js
- /home/jetson/.cursor-server/cli/servers/Stable-51c8aff7cb5a89f4a0e462fbacab938bdbfaf140/server/out/vs/loader.js
- /home/jetson/.cursor-server/cli/servers/Stable-51c8aff7cb5a89f4a0e462fbacab938bdbfaf140/server/out/bootstrap-amd.js
- /home/jetson/.cursor-server/cli/servers/Stable-51c8aff7cb5a89f4a0e462fbacab938bdbfaf140/server/out/bootstrap-fork.js.

```

---

<div class="post-metadata">

**Author:** ![qirui-chen-9](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/qirui-chen-9/32/7046_2.png) [@qirui-chen-9](https://forum.cursor.com/u/qirui-chen-9)\
**Post date:** [October 7, 2024, 2:09pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/11 "2024-10-07T14:09:36Z")

</div>

Hi netcaster, I download the 0.40.4 and work fine.  
but Cursor auto update to last version 0.41.3, do you know how to disable the auto update?

thanks.

---

<div class="post-metadata">

**Author:** ![netcaster](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/netcaster/32/6215_2.png) [@netcaster](https://forum.cursor.com/u/netcaster)\
**Post date:** [October 7, 2024, 2:36pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/12 "2024-10-07T14:36:13Z")

</div>

You can find the steps in my Twitter post.  
But it is only for windows

> <https://x.com/netcaste/status/1838897569948479911?s=19>

---

<div class="post-metadata">

**Author:** ![aar2dee2](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/aar2dee2/32/6437_2.png) [@aar2dee2](https://forum.cursor.com/u/aar2dee2)\
**Post date:** [October 7, 2024, 3:12pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/13 "2024-10-07T15:12:13Z")

</div>

Having trouble with codebase indexing and adding new docs on local as well.  
system: macOS

 ![Screenshot 2024-10-07 at 8.41.05 PM](https://us1.discourse-cdn.com/cursor1/original/2X/0/0880547ac529f0aa1f2c0f3d5db1d4021e8c75b7.png)

---

<div class="post-metadata">

**Author:** ![yuthon](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuthon/32/8050_2.png) [@yuthon](https://forum.cursor.com/u/yuthon)\
**Post date:** [October 11, 2024, 4:08am UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/14 "2024-10-11T04:08:17Z")

</div>

Workaround for `Cannot find module '@anysphere/file-service-linux-arm64-gnu'` Error

To resolve the error `Cannot find module '@anysphere/file-service-linux-arm64-gnu'`, we can manually install the package. This issue occurs because the remote VS Code server initialization mistakenly installs the x64 version instead of the arm64 version.

Target Directory:

```auto
~/.cursor-server/cli/servers/Stable-<version>/server/extensions/cursor-retrieval/node_modules/@anysphere

```

Replace `<version>` with your specific Cursor version.

Important: Use the same version as the original `file-service-linux-x64-gnu`, e.g., `0.0.0-51333e36-6e776f2305a251cf73bd51c4fcdf375334c99ed76a393f3b4efd90b6eace2b69`.

Directory structure before and after the fix:

```bash
# Before
$ ls ~/.cursor-server/cli/servers/Stable-9e8f0f993884031e2f08d75f7adab80d1732a980/server/extensions/cursor-retrieval/node_modules/@anysphere
file-service file-service-linux-x64-gnu

# After
$ ls ~/.cursor-server/cli/servers/Stable-9e8f0f993884031e2f08d75f7adab80d1732a980/server/extensions/cursor-retrieval/node_modules/@anysphere
file-service file-service-linux-arm64-gnu file-service-linux-x64-gnu

```

After applying the fix, reload the Cursor workspace. This solution has been tested and confirmed working on my MacBook Pro (host: arm64 macOS, remote: arm64 Linux).

---

<div class="post-metadata">

**Author:** ![trevordcampbell](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/trevordcampbell/32/5652_2.png) [@trevordcampbell](https://forum.cursor.com/u/trevordcampbell)\
**Post date:** [October 11, 2024, 10:37pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/15 "2024-10-11T22:37:41Z")

</div>

> [@yuthon](#):
>
> Workaround for `Cannot find module '@anysphere/file-service-linux-arm64-gnu'` Error

Amazing find dude — This works for me! 🎉

A bit annoying that I might have to do this for every new container until they actually fix it, but at least it works and codebase indexing can function inside a dev container now!

A couple of notes for anyone else trying this workaround:

- The directory structure in my container was a little bit different from @yuthon’s– the needed path that contained the file-service and file-service-linux-x64-gnu packages was located at the directory (You might have to do some `ls` or `ls -all` hunting in terminal to find the right directory):

```auto
~/.cursor-server/bin/<version>/extensions/cursor-retrieval/node_modules/@anysphere

```

- If it wasn’t clear, use the command `npm install @anysphere/file-service-linux-arm64-gnu` to install the needed service

- When installed it, for some reason it deleted the existing `file-service` and `file-service-linux-x64-gnu` packages after successfully installing `file-service-linux-arm64-gnu`

Ultimately, my final subdirectory structure looks like this:

```auto
# Before
$ ls ~/.cursor-server/bin/51c8aff7cb5a89f4a0e462fbacab938bdbfaf140/extensions/cursor-retrieval/node_modules/@anysphere
file-service file-service-linux-x64-gnu

# After
$ ls ~/.cursor-server/bin/51c8aff7cb5a89f4a0e462fbacab938bdbfaf140/extensions/cursor-retrieval/node_modules/@anysphere
file-service file-service-linux-arm64-gnu

```

And with this workaround, indexing now works inside a Dev Container for me again after rebuilding / restarting the container:

 ![Screenshot 2024-10-11 at 6.34.02 PM](https://us1.discourse-cdn.com/cursor1/original/2X/b/b7b8d7dc8e78fd36d7d228944ef22fd8ef3cffff.png)

---

<div class="post-metadata">

**Author:** ![maxritter](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/maxritter/32/20633_2.png) [@maxritter](https://forum.cursor.com/u/maxritter)\
**Post date:** [October 14, 2024, 6:24am UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/17 "2024-10-14T06:24:43Z")

</div>

@trevordcampbell Thanks for helping with this! I did as you described, but unfortunately this did not work for me. What worked in the end was:

1. Open your Dev Container in Cursor, in the terminal execute: `rm -rf ~/.cursor-server/bin/ && rm -rf /vscode/cursor-server/` to clean-up Cursor Server
2. Relaunch Cursor, it will now re-download the Cursor Server for your current version
3. In your Dev Container and Terminal, go into the Binary folder (`cd /vscode/cursor-server/bin/linux-arm64/`) and into the one version that has been newly downloaded, f. ex. `c499aee5f16e67815c7dc795ff338dc8ab3e07f0`
4. Cd into the File-Service Module: `cd extensions/cursor-retrieval/node_modules/@anysphere/`#
5. Run `ls`, we expect to see `file-service` and `file-service-linux-x64-gnu`, which is the wrong platform and we want to change that against `file-service-linux-arm64-gnu`
6. Run `npm ls` and copy the version of the currently installed file-service package, f. ex. `@anysphere/file-service@0.0.0-51333e36-b5a1ea2b87155ab8ae516f33ff320ebbd21e10de5b9276996ce3c3e44dbd1a83`
7. Yarn add this package together with the missing ARM64 package: `yarn add @anysphere/file-service@0.0.0-51333e36-b5a1ea2b87155ab8ae516f33ff320ebbd21e10de5b9276996ce3c3e44dbd1a83 @anysphere/file-service-linux-arm64-gnu`
8. Relaunch Cursor and Indexing should work again!

 ![Screenshot 2024-10-14 at 08.23.33](https://us1.discourse-cdn.com/cursor1/original/2X/6/6edaf88330c8c6a7e27cdec452057433c72ab3ed.png)

---

<div class="post-metadata">

**Author:** ![hbd](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/hbd/32/8651_2.png) [@hbd](https://forum.cursor.com/u/hbd)\
**Post date:** [October 15, 2024, 10:17pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/18 "2024-10-15T22:17:24Z")

</div>

Thanks for the info all. Curious - are you also seeing the “Review” tab infinitely load (without the fix)? I’m seeing both behaviors when working in a dev container.

---

<div class="post-metadata">

**Author:** ![cneskey](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/cneskey/32/10483_2.png) [@cneskey](https://forum.cursor.com/u/cneskey)\
**Post date:** [November 1, 2024, 12:03pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/19 "2024-11-01T12:03:43Z")

</div>

This has been working for me but I have to run it on each new container.

```shell
#!/bin/bash
rm -rf ~/.cursor-server/bin/ && rm -rf /vscode/cursor-server/
version=$(ls ~/.cursor-server/bin/ | grep -E '^[0-9a-f]{40}$')
printf "version: $version\n"
cd ~/.cursor-server/bin/$version/extensions/cursor-retrieval/node_modules/@anysphere
npm install @anysphere/file-service-linux-arm64-gnu --silent
npm install @anysphere/file-service --silent

```

---

<div class="post-metadata">

**Author:** ![i.guinea](https://avatars.discourse-cdn.com/v4/letter/i/41988e/32.png) [@i.guinea](https://forum.cursor.com/u/i.guinea)\
**Post date:** [November 5, 2024, 12:57pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/20 "2024-11-05T12:57:49Z")

</div>

Thanks for the workaround! but i didn´t manage to make it run.

Followed steps:

- Remove directories  
`rm -rf ~/.cursor-server/bin/ && rm -rf /vscode/cursor-server/`

- Disconnect from container y connect again

- Other steps from your script (done this way cause couldn´t query installed version if removed first)

```auto
version=$(ls ~/.cursor-server/bin/ | grep -E '^[0-9a-f]{40}$')
printf "version: $version\n"
cd ~/.cursor-server/bin/$version/extensions/cursor-retrieval/node_modules/@anysphere
npm install @anysphere/file-service-linux-arm64-gnu --silent
npm install @anysphere/file-service --silent

```

- Disconnect from container y connect again
- Get the followin error:

```auto
2024-11-05 13:52:14.782 [info] Creating merkle client.
2024-11-05 13:52:14.782 [info] Done creating merkle client.
2024-11-05 13:52:14.782 [info] Doing a startup handshake.
2024-11-05 13:52:14.808 [error] TypeError: this.merkleClient.initWithRipgrepIgnore is not a function
at S.initializeMerkleTreeWithRipgrepIgnore (/vscode/cursor-server/bin/linux-arm64/b1e87884330fc271d5eb589e368c35f14e76dec0/extensions/cursor-retrieval/dist/main.js:2:826004)
at S.getServerStatus (/vscode/cursor-server/bin/linux-arm64/b1e87884330fc271d5eb589e368c35f14e76dec0/extensions/cursor-retrieval/dist/main.js:2:823904)
at async S.startIndexingRepository (/vscode/cursor-server/bin/linux-arm64/b1e87884330fc271d5eb589e368c35f14e76dec0/extensions/cursor-retrieval/dist/main.js:2:826840)
2024-11-05 13:52:14.808 [info] Indexing job successfully done or aborted.

```

---

<div class="post-metadata">

**Author:** ![atur-yo](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/atur-yo/32/6969_2.png) [@atur-yo](https://forum.cursor.com/u/atur-yo)\
**Post date:** [November 6, 2024, 5:13pm UTC](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858/21 "2024-11-06T17:13:57Z")

</div>

Same issue here, it make indexation fail which is the most interesting feature to me. Hope it ll be fixed soon.

[Next page](https://forum.cursor.com/t/codebase-indexing-no-longer-working-inside-dev-containers/17858.md?page=2)
