Could not resolve URI: Unable to resolve nonexistent file ... [composer] [devcontainer]

Bug Report
1

Describe the Bug

I’m seeing “Could not resolve URI: Unable to resolve nonexistent file …” when using Composer in a devcontainer. Seems to have broken in a recent update, since composer worked prior to December 27 in this codebase.

The following is my dev container config:

{
  "name": "Django API",

  // This devcontainer uses the docker-compose file so that we can connect to other services
  "dockerComposeFile": "../docker-compose.yml",
  "service": "dev",
  "runServices": ["db", "redis"],
  "workspaceFolder": "/app",
  "customizations": {
    "vscode": {
      "settings": {},
      "extensions": ["ms-python.python", "ms-python.vscode-pylance"]
    }
  }
}

Steps to Reproduce

Try using Composer in a devcontainer.

Screenshots / Screen Recordings

CleanShot 2025-01-08 at 15.23.13.png
CleanShot 2025-01-08 at 15.23.13.png764×284 28.5 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.1.0

Additional Information

NA

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Cursor agent support in dev containers is not great at the moment, but we’re working hard to increase stability and support around this at the moment.

We will hopefully have some improvements available in our next update.

1 Like
3

@hbd I’m desperately trying to get the basic dev container commands working, but alas. Can you help me out by telling which extensions you installed to make it work please?