After that it rebuild the current devcontainer and updated the extensions. After the window reload I stuck with the following message:
[7 ms] Dev Containers 0.394.0 in VS Code 1.96.2 (f06cc5e62b757b2bf61ec052a8701fb2da9ded20).
[7 ms] The Dev Containers extension is supported only in Microsoft versions of VS Code
have a base account repo. Into it various aspects of your logic and outputs and context reside.
When adapting to a new model, new agentic platform, or a latest update - put the agents through validation testing and USER ACCEPTANCE TESTING that the IDE (which is now the agent) can seamlessly move forward and wont backward break â– â– â– â– ?
Should there be an agentic versioning handoff?
Are there internal release notes that can be back-propagated to the existing agentic install such as:
"Im about to update to this [URL to release code that agents can slurp] – and I want you to evaluate our @codebase for any adjustments that need be written/done/logged/communicated – and give me a detailed rollout with rollback.
Could you try uninstalling and reinstalling the extension.
And if that does not work, could you try removing the extension: rm -r ~/.cursor/extensions/extension-name, then reinstall. Then restart Cursor via cmd+shift+p > reload window
We published our own extension for dev containers. If it’s still not working for you, could you try uninstalling the existing extension, and then install the Cursor remote containers extension? You can find it by searching for @id:anysphere.remote-containers in the extension search box. (Attaching a screenshot)
Hi! Could you check this error that occurs when I try to attach to the docker conatiner with anysphere.remote-containers?
my cursor version is 0.50.5, the extension version is 0.0.12
I can attach using vscode but cannot with cursor.
[Error - 06:53:55.284] Failed to install remote server in container: Error: Failed to install remote server in container: Error: Command failed with exit code 1: stdout: Killing all running Cursor servers
No running servers found
Killing running servers:
Removing all existing Cursor installations
removed '/root/.cursor-server/bin/96e5b01ca25f8fbd4c4c10bc69b15f6228c80770/node_modules/https-proxy-agent/dist/index.d.ts.map'
...
removed directory '/root/.cursor-server/bin'
removed '/root/.cursor-server/.installation_lock'
Waiting for lock...
Lock acquired, proceeding with installation.
Installing server script
Cursor server path: /tmp/cursor-server-89252217-de94-4624-bd17-71b9fe9d1579.tar.gz
Using provided cursor server path: /tmp/cursor-server-89252217-de94-4624-bd17-71b9fe9d1579.tar.gz
Error server did not start successfully
Server log file: /root/.cursor-server/.96e5b01ca25f8fbd4c4c10bc69b15f6228c80770.log
Segmentation fault
and server log file is just “Segmentation Fault”
Thanks – I tried building a similar issue and wasn’t able to reproduce it. Would you be able to rm -rf /root/.cursor-server within the container, and try again?
If that doesn’t work, would you be able to create a new dev container? You can do so by running docker rm -fv <container id>. Note that this would cause any ephemeral state that is not stored inside a bind mount or named volume to be lost.