[SOLVED] Devcontainers in 0.44

Discussion
1

I think v0.44.1 doesn’t work with devcontainers v0.394.0

2024-12-18 13:31:12.459 [error] command 'remote-containers.openDevContainerFile' not found: Error: command 'remote-containers.openDevContainerFile' not found
    at h.n (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2916:32878)
    at h.executeCommand (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2916:32807) command 'remote-containers.openDevContainerFile' not found

Does anyone have a direct download link to download latest point-release of v0.43 for macOS/ARM (which was working fine with devcontainers)

3 Likes
2

https://dl.todesktop.com/230313mzl4w4u92/versions/0.43.6/mac/zip/arm64

^Overwriting Cursor v0.44.0 with the above v0.43.6 version and a “restart extension” on the devcontainer back to v0.327.0 and this is now fixed.

Clearly the devcontainer workflow is never validated with Cursor QA process.

1 Like
3

Quite surprising that they are not using dev container themselves, since they use Cursor to build Cursor. There is not much reason not to use dev container nowadays.

Are they still using 1.93 in 0.44?

4

Yes. I suspect the Cursor team isn’t handling the “automatic update” functionality of 3rd-party extensions, so when Cursor “Attempt(s) Update”, the extensions like “devcontainer” also try to auto-update from say v0.327.0 → v0.395.0 (latest available and working just fine in VS Code v1.96 released last week), is I think the Cursor team have “pinned” the devcontainer version to their forked v1.93 VS Code, which is now 3-months behind.

The age-old adage always applies to forking open-source: “No such thing as a free lunch”. If your gonna fork VS Code, then expect to invest in dev effort to keep cadence with each release.

5

So your workaround is to downgrade Cursor back to .43 or there is a way to downgrade the dev container extension?

6

@mjnowen

Thanks to your post on this thread, I now understand why DevContainer suddenly stopped working in my environment. Thank you so much.

I managed to resolve the issue by downgrading to version 43.6 and forcibly disabling AutoUpdate.
However, I find it puzzling that Cursor does not provide a way to disable AutoUpdate in their function menu.

7

How did you forcibly disable Cursor from updating? I’m stuck in a world where upon restarts of Cursor, it will always update to v0.44.0 now.

The added issue is even if I disable the “devcontainer” extension from “Auto Update” to try and keep it at v0.327.0, which seems to work with VS Code v1.93 (cursor current fork), upon restart, it still auto updates to “v0.394.0” <–which I believe is the new MSFT released devcontainer version (since 11th Dec 2024) which now breaks Cursor.

So, my current bandaid is simply to ignore the “1” blue circle in my “Extensions” window AND not shutdown/restart Cursor; which of course is not maintable…so I need the Cursor team to resolve this issue at their end.

The simplest option is expose a setting to allow customers to DISABLE CURSOR from updating itself automatically. Better still, provide a feature/GUI to allow customers to download and pin to a known good version of Cursor…

OR…release a newer version of Cursor that is forked from VS Code v1.96 + v0.394.0 devcontainer, which is working fine when I switch back to VS Code; which is my final option if I need to dump Cursor.

8

It’s starting to pop in this forums, lot of extension are breaking and I expect more to do so, the VS Code build they use is simply too old at this point. I don’t think Cursor have been so far behind the VS Code official build then now. That’s what is annoying with a forked version, would be better to get everything in VS Code, but unfortunately it’s not possible.

9

I have also encountered and tracked this exact issue. Hoping for a fix soon

11

Hi @mjnowen

How did you forcibly disable Cursor from updating?

I just followed this topic:

I am a Windows user, so this might not directly help you, but here’s what I did:

  1. Go to %USERPROFILE%/AppData/Local/Programs/cursor/resources.
  2. Find a file named auto-update.yaml.
  3. Empty the file (make it blank).
  4. Go to the folder %USERPROFILE%/AppData/Local/cursor-updater.
  5. Delete everything in that folder.

This method is a bit rough, but it works perfectly fine in my environment.
It stopped Cursor from showing small update notifications, and it never updated to version 44.

Hope this helps!

12

Hey,

We have identified this issue and are working on deploying a fix.
For users who are on v0.44 already, it should roll out to you within the next 12-24 hours, possibly in a few hours if all goes to plan!

13

FYI. If this fix is v0.44.2, then it is still broken.

1 Like
14

it’s working again now

15

This should be fixed in 0.44.3

2 Likes
16

Unfortunately, on Windows 11 it still does not work. I had to downgrade to 0.43.6 to be able to work. Already sent an issue through an embedded tool.

1 Like
17

Are you sure? Could you share the logs and details with 0.44.3 or 0.44.4?

18

It’s working here with macOS

@amanrs I have other extensions crashing that works fine on VS Code (like ElixirLS), I think it’s due to VS Code being 1.93 which is very old at this point, can we expect an update to 1.96 soon?

indexing inside a Dev container is still broken

image
image1540×354 27.7 KB

19

Definitely. I could gladly provide you logs and anything you need, just tell me what to do.
EDIT: I have event tried preventing Cursor from updating because of this but somehow it is still updating and breaking devcontainers.