codesandbox / codesandbox/codesandbox-client

VSCode Server Fails to Start When Creating Docker Project: "/vscode/1.89.1.24130/node: not found"

Open
#8,616 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

image

🐛 bug report

Preflight Checklist

  • I have read the [Contributing Guidelines][contributing] for this project.
  • I agree to follow the [Code of Conduct][code_of_conduct] that this project adheres to.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.

Description of the problem

When attempting to create a project in CodeSandbox using the Docker template, the process gets stuck at the VS Code server boot up stage. The server fails to start, preventing the project from being created.

How has this issue affected me ? What am I trying to accomplish?

This issue is preventing me from creating and working on a Docker-based project in CodeSandbox. I'm unable to proceed with my development work due to this error.

To Reproduce
  1. Open CodeSandbox
  2. Attempt to create a new project using the Docker template
  3. Wait for the project to initialize
  4. Observe that the process gets stuck at "Starting VSCode server..."
  5. Check the console output, which shows an error: "/vscode/1.89.1.24130/node: not found"
Link to sandbox: link (optional)

(https://codesandbox.io/p/github/thefatdeveloper/nginx-docker-example/main?workspaceId=17d20f2e-9c30-4441-8067-800d0e9d3ceb)

Need Help in resolving this.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Docker template project and inspect the console output during the “Starting VSCode server...” stage. The work is done when the VSCode server starts successfully and the Docker project finishes creating without the “/vscode/1.89.1.24130/node: not found” error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, javascript, vscode
Domain
devops, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.