da1z
February 13, 2026, 9:52pm
1
Describe the Bug
long running agent can not start due to docker build issue
Steps to Reproduce
run long running anent
Expected Behavior
works
Screenshots / Screen Recordings
Operating System
MacOS
Version Information
Version: 2.4.36 (Universal)
VSCode Version: 1.105.1
Commit: f9919bf991f247689f9ead605b5c5a3239a2a790
Date: 2026-02-12T21:00:33.976Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0
Does this stop you from using Cursor
Yes - Cursor is unusable
deanrie
(Dean Rie)
February 14, 2026, 6:35am
3
Hey, thanks for the report. The key issue in the logs is transferring dockerfile: 2B done. That means only 2 bytes are being sent to the Docker build, basically an empty Dockerfile. That’s why the build fails.
A few things to check:
Can you share the contents of .cursor/environment.json? Especially the build section. It should point to your Dockerfile примерно like this:
{
"build": {
"context": ".",
"dockerfile": ".cursor/Dockerfile"
}
}
What’s in your Dockerfile, and where is it located? It should be in .cursor/ (or wherever your environment.json points).
Did you create a snapshot after adding the Dockerfile? (Cmd+Shift+P > Cursor: Start Cloud Agent Setup)
Most likely the Dockerfile path in environment.json doesn’t match the file’s actual location, or the file is empty or missing from the build context.
Docs: Cloud Agents | Cursor Docs (see “Manual Setup with Dockerfile”).
Let me know what you find.
da1z
February 14, 2026, 4:14pm
4
the thing is do not use docker. i set “use default image” and i do not have enveroment.json and docker file
da1z
February 17, 2026, 3:12pm
5
switch to docker and back to default seems to solved it