Devctonainer issues on 2.0.75

[LordWaffleman]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I fired up Cursor 2.0.75 and set up a very basic container for a Golang project. Upon loading up the IDE, it just hangs and never loads the project even with successful startup.

This was previous working until I fired up the new version of Cursor and I made no changes.

Steps to Reproduce

1. Create a basic devcontainer setup - base image is golang:1.25.3-bookworm, no dependencies
2. Re-launch the IDE into the project
3. Allow container to build (note success)
4. Wait for completion and note that project never loads
5. Check the logs (no errors, no warnings)

Expected Behavior

One of the following:

1. An error shows explaining that the container failed
2. The project loads

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.75
VSCode Version: 1.99.3
Commit: 9e7a27b76730ca7fe4aecaeafc58bac1e2c82120
Date: 2025-11-12T17:34:21.472Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.17.4-76061704-generic

Additional Information

I also did the following:

• nuke everything Docker
• try additional projects that were previously working

Docker Version

Client: Docker Engine - Community
 Version:           29.0.0
 API version:       1.52
 Go version:        go1.25.4
 Git commit:        3d4129b
 Built:             Mon Nov 10 21:46:03 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          29.0.0
  API version:      1.52 (minimum version 1.44)
  Go version:       go1.25.4
  Git commit:       d105562
  Built:            Mon Nov 10 21:46:03 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v2.1.5
  GitCommit:        fcd43222d6b07379a4be9786bda52438f0dd16a1
 runc:
  Version:          1.3.3
  GitCommit:        v1.3.3-0-gd842d771
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Files

All of the following is in the {PROJECT_ROOT}/.devcontainer folder.

devcontainer.json

{
	"name": "MyApp",
	"dockerComposeFile": "docker-compose.yml",
	"service": "app-devcontainer",
	"workspaceFolder": "/workspace",
	"shutdownAction": "stopCompose",
	"customizations": {
		"vscode": {
			"extensions": [
				"golang.go",
				"ms-azuretools.vscode-docker"
			],
			"settings": {
				"go.toolsManagement.checkForUpdates": "local",
				"go.useLanguageServer": true,
				"go.gopath": "/go",
				"go.goroot": "/usr/local/go"
			}
		}
	},
	"forwardPorts": [8080],
	"portsAttributes": {
		"8080": {
			"label": "API",
			"onAutoForward": "notify"
		}
	},
	"postCreateCommand": "go mod download",
	"remoteUser": "appdev"
}

Dockerfile

FROM golang:1.25.3-bookworm

# install standard tools
RUN apt-get update && apt-get install -y git curl && \
    rm -rf /var/lib/apt/lists/*

# create a non-root user
ARG USERNAME=appdev
ARG USER_UID=1000
ARG USER_GID=${USER_UID}

RUN groupadd --gid ${USER_GID} ${USERNAME} && \
    useradd --uid ${USER_UID} --gid ${USER_GID} -m ${USERNAME}

# set up Go environment
ENV GOPATH=/go
ENV PATH=$PATH:/usr/local/go/bin:$GOPATH/bin

# install Go tools
#  - gopls: Go language server (for code completion, formatting, and linting)
#  - dlv: Go debugger (for debugging Go code)
RUN go install golang.org/x/tools/gopls@latest && \
	go install github.com/go-delve/delve/cmd/dlv@latest

# switch to non-root user
USER $USERNAME

WORKDIR /workspace

docker-compose.yml

services:
  app-devcontainer:
    build:
      context: .
      dockerfile: Dockerfile
    volumes:
      - ..:/workspace:cached
    command: sleep infinity
    networks:
      - myapp

networks:
  myapp:
    name: myapp

Does this stop you from using Cursor

Yes - Cursor is unusable

[LordWaffleman]

Odd. I started it up and at one point it connect, but I can’t reproduce the connection.

[raphaelcamus]

I had the issue, and it appears that is was due to docker 29 and its breaking changes (minimal API change). Downgrading to latest 28.x solves the problem:

sudo apt remove docker-ce docker-ce-cli docker-buildx-plugin docker-compose-plugin
sudo apt install docker-ce=5:28.5.2-1~ubuntu.24.04~noble docker-ce-cli=5:28.5.2-1~ubuntu.24.04~noble docker-buildx-plugin=0.14.0-1~ubuntu.24.04~noble docker-compose-plugin=2.27.0-1~ubuntu.24.04~noble
sudo apt-mark hold docker-ce docker-ce-cli docker-buildx-plugin docker-compose-plugin

[TP_Honey]

this works for me, thanks for the tip. it had all of a sudden failed for me.

downgrading docker is a pain though.
of note is the dev container extension for vs-code handles this, albeit not gracefully.

[raphaelcamus]

I was having the same issue with VS code too. I don’t get your comment “dev container extension for vs-code handles this, albeit not gracefully”

Note that I had the issue with portainer too yesterday, and when seraching the net, it loks like a lot of docker “consumers” are facing this issue. I hope this new docker will be handled soon, so we can keep on upgrading docker and so get the latests fixes

[LordWaffleman]

That worked like a charm. I didn’t even think of rolling back Docker.

[ravirahman]

Hi all, thank you for this bug report. Could you try upgrading to version 1.0.28 of the Anysphere Remote Containers extension? This version includes a newer version of the devcontainers CLI which should fix this issue.

[lokimon]

Seems to work for me.
Thanks!

[LordWaffleman]

This seems to be fixed now.