Long opening of dev container

[Skybydyshh]

Describe the Bug

long opening dev container after the logs on the screen. In addition to this, I get a notification every time about installing an extension for dev conainers, but I already have it installed. After these logs, after about 5 minutes, there is a log like this: Finished installing remote server in container. Output: Waiting for lock…

maybe for some reason it tries to install something again every time

Steps to Reproduce

opening a folder in wsl, then the reopen in contaner function

Expected Behavior

quick start dev containers. No notification about installing dev containers

Screenshots / Screen Recordings

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Версия: 1.1.6 (user setup)
Фиксация: 1.96.2
Дата: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Electron: 2025-06-25T02:20:02.577Z
ElectronBuildId: 34.5.1
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.0
ОС: 13.2.152.41-electron.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

[ravirahman]

If it’s taking that long, it sounds like it’s rebuilding the container every time. Could you share the full logs, which would indicate the timestamps?

Re: the duplicate notification, this will be fixed in version 1.2 of Cursor.

[Skybydyshh]

logs.txt (58,7 КБ)

here it was faster, 2 and a half minutes. But in any case, in vc code both rebuild and open are executed much faster. I have a strong feeling that something is wrong with my cursor. Cursor server path: undefined for some reason. Please read my logs, I will be very grateful

I also noticed that after opening the container, ports stopped being forwarded automatically. This setting in devContainer does not work
“forwardPorts”: [
5444, // PostgreSQL
7000, // Application
3000, // Grafana
9090 // Prometheus
],