Most of my projects / code use VS Code Dev containers, and I’m not able to successfully build and open in these containers… wondering what’s the workaround?
For example, getting this error when the devcontainer is being built…
failed to solve: dev_container_feature_content_temp: failed to resolve source metadata for docker.io/library/dev_container_feature_content_temp:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
[2024-04-23T16:29:22.142Z] Stop (2150 ms): Run: docker-compose --project-name #redacted# -f /Users/#redacted#/code/#redacted#/docker-compose.yml -f /Users/#redacted#/code/#redacted#/.devcontainer/docker-compose.dev.yml -f /Users/#redacted#/Library/Application Support/Cursor/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.build-1713889759992.yml build
[2024-04-23T16:29:22.143Z] Error: Command failed: docker-compose --project-name #redacted# -f /Users/#redacted#/code/#redacted#/docker-compose.yml -f /Users/#redacted#/code/#redacted#/.devcontainer/docker-compose.dev.yml -f /Users/#redacted#/Library/Application Support/Cursor/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.build-1713889759992.yml build
[2024-04-23T16:29:22.143Z] at pw (/Users/#redacted#/.cursor/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:427:522)
[2024-04-23T16:29:22.143Z] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[2024-04-23T16:29:22.143Z] at async L$ (/Users/#redacted#/.cursor/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:427:2493)
[2024-04-23T16:29:22.143Z] at async N$ (/Users/#redacted#/.cursor/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:409:3165)
[2024-04-23T16:29:22.143Z] at async tAA (/Users/#redacted#/.cursor/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:479:3833)
[2024-04-23T16:29:22.143Z] at async CC (/Users/#redacted#/.cursor/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:479:4775)
[2024-04-23T16:29:22.143Z] at async NeA (/Users/#redacted#/.cursor/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:612:11107)
[2024-04-23T16:29:22.143Z] at async MeA (/Users/#redacted#/.cursor/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js:612:10848)
[2024-04-23T16:29:22.147Z] Stop (6552 ms): Run: /Applications/Cursor.app/Contents/Frameworks/Cursor Helper (Plugin).app/Contents/MacOS/Cursor Helper (Plugin) /Users/#redacted#/.cursor/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /Users/#redacted#/Library/Application Support/Cursor/User/globalStorage/ms-vscode-remote.remote-containers/data --docker-path podman --container-session-data-folder /tmp/devcontainers-b754c523-9178-478d-933d-b7c45eb640e11713889754028 --workspace-folder /Users/#redacted#/code/#redacted# --workspace-mount-consistency cached --id-label devcontainer.local_folder=/Users/#redacted#/code/#redacted# --id-label devcontainer.config_file=/Users/#redacted#/code/#redacted#/.devcontainer/devcontainer.json --log-level debug --log-format json --config /Users/#redacted#/code/#redacted#/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --remove-existing-container --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root
[2024-04-23T16:29:22.147Z] Exit code 1
[2024-04-23T16:29:22.149Z] Command failed: /Applications/Cursor.app/Contents/Frameworks/Cursor Helper (Plugin).app/Contents/MacOS/Cursor Helper (Plugin) /Users/#redacted#/.cursor/extensions/ms-vscode-remote.remote-containers-0.327.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /Users/#redacted#/Library/Application Support/Cursor/User/globalStorage/ms-vscode-remote.remote-containers/data --docker-path podman --container-session-data-folder /tmp/devcontainers-b754c523-9178-478d-933d-b7c45eb640e11713889754028 --workspace-folder /Users/#redacted#/code/#redacted# --workspace-mount-consistency cached --id-label devcontainer.local_folder=/Users/#redacted#/code/#redacted# --id-label devcontainer.config_file=/Users/#redacted#/code/#redacted#/.devcontainer/devcontainer.json --log-level debug --log-format json --config /Users/#redacted#/code/#redacted#/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --remove-existing-container --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root
[2024-04-23T16:29:22.149Z] Exit code 1
hmm, honestly, I am finding that thread very hard to follow - not an expert here. I have no trouble running dev containers in VS Code on the very same device, it’s just it doesn’t work with Cursor - if that helps.
Sorry, I’m not sure what is meant here? My original issue above is that the dev container is not even getting built… it’s failing (as shown in the logs above). So there’s no way for me to connect and delete anything inside of it, for a container that isn’t even running yet?
I had switched back to VS code a while back due to this issue, so I Just reinstalled Cursor right now to the latest version, and tried building and opening the project in dev container. Still breaking:
Hey @amanrs - wondering if the information I provided above is useful and any luck on this front? really can’t wait for Cursor to have dev containers support!
Same problem here on Ubuntu 24.04. DevContainer works in VSCode, fails in Cursor. Error along these lines:
The editor could not be opened due to an unexpected error:
ENOPRO: No file system provider found for resource
'vscode-remote://dev-container%2B7b22686f737
This is such an important feature that I’m truly surprised Cursor’s enterprise customers have not flagged it as “deal breaker” yet.
In the meantime, I implemented a shell wrapper script that connects into the project’s container by detecting VSCode’s shell integration.
My implementation is very specific to how we manage local environments in my company, but I thought this would at least be interesting and useful for some of you and, hopefully, point you into a useful workaround