Infinite loading after pressing Reopen in container

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After reopening a previously working Dev Container via Reopen in Container command, the editor gets stuck in an infinite loading state. Nothing is displayed in terminal.
It used to work last week. No changes in container since then. I only updated the Cursor to latest version.

Error is thrown by Remote Containers extension.

Failed to install Cursor server: Failed to run devcontainer command: 1. {"outcome":"error","message":"An error occurred running user commands in the container.","description":"An error occurred running user commands in the container."}

Screenshot 2026-06-01 at 14.17.29
Screenshot 2026-06-01 at 14.17.292562Ă—1404 151 KB

Steps to Reproduce

  1. Open a project workspace with a functional Dev Container configuration.
  2. Click Reopen in Container (from the Dev Container context menu).

Operating System

MacOS

Version Information

Version: 3.6.31
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Darwin arm64 25.5.0

Identifier: anysphere.remote-containers
Version: 1.0.35
Last Updated: 2026-05-29, 06:47:25

Does this stop you from using Cursor

Yes - Cursor is unusable

6

This is something we’ve seen before with Dev Containers after Cursor updates. The error you’re getting (“An error occurred running user commands in the container”) is unfortunately generic, so we need a bit more info to pinpoint the cause.

Could you share the following?

  1. Dev Containers output log: Open View > Output, then select “Dev Containers” from the dropdown on the right. Try “Reopen in Container” again, and share the full output that appears before and after the error.

  2. Your devcontainer.json file contents (or the relevant parts, especially any postCreateCommand, postStartCommand, initializeCommand, or other lifecycle commands).

  3. Docker Desktop version: You can find this in Docker Desktop > Settings > About.

  4. Remote Containers extension version: In the Extensions panel, check the version number for “Remote Containers” by Anysphere (should be something like 1.0.32 or 1.0.35).

Also, two things worth trying:

  • Rebuild the container: Run Dev Containers: Rebuild Container from the Command Palette (Cmd+Shift+P). This forces a clean rebuild instead of reattaching to the existing one.

  • Check for extension updates: Open the Extensions panel (Cmd+Shift+X), search for “Dev Containers” (Anysphere), and make sure you’re on the latest version. A recent fix (v1.0.35) addressed some devcontainer lifecycle issues.

The Dev Containers output log is the key diagnostic here – it will show exactly which step is failing and why.

7

Got the same error.

No log shown. You can’t display the “Dev Containers” Output view as the IDE keep loading.

@Florentina_Petcu
To fix this I downgraded the extension “Dev Containers” to the previous version: 1.0.34