-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code - OSS
doesn't launch when using Dev Container locally or in codespaces
#168655
Comments
Maybe Christoph could advice how to setup the container to allow to run VS Code given his work in this field. |
I was going to setup my dev environment the "normal" way, but then I noticed the dev container config and thought it would be cool to try that out :) Thanks in advance for helping! |
@alexdima Not sure how to debug this, there is an empty event object coming from https://github.com/microsoft/vscode/blame/d735856fd9e156d46f11bff0a7cf5ed5c9610ddc/src/vs/loader.js#L654 for many or all script files. |
Hi! I have the same issue OS VERSION: VS CODE: [EDIT] Updated OS build to 22621.963 and the issue still persist. |
Is there anything that can be done about this or is there an ETA for when? I'd love to get started with solving issues for the VSCode project :D |
Needs further investigation. We will also add a simpler configuration that should hopefully be more robust as part of #170969. |
@bpasero @deepak1556 The following is burried in all the other log messages, could this be the root cause? Interestingly the Insiders build works in the container.
|
I am not sure I follow, isnt this about running VSCode out of sources in a container? How is insiders related? |
I don't know if it is relevant, but the problem when running out of sources doesn't reproduce with Insiders when run in the same container. |
@deepak1556 I have run Git bisect on this: 1044556 is the first bad commit |
Still encountering this from
See following stdout, however for X11 forwarding, the stdout
Using the prebuilt
Not being able to open the file descriptor wouldn't be related to docker's changing default for LimitNOFILE would it?
My system info if at all helpful: VS Code version: Code 1.77.1 (b7886d7, 2023-04-04T23:21:11.906Z) System Info
Extensions (11)
A/B Experiments
|
Upstream issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1263267 Please start with |
Does this issue occur when all extensions are disabled?: Yes
I was trying to get a development VS Code OSS build running with dev containers. After following the steps from https://github.com/microsoft/vscode/tree/main/.devcontainer, I only got the following error when trying to execute
bash scripts/code.sh
:My
yarn
/yarn install
command beforehand runs without errors.The noVNC web interface shows this:
The text was updated successfully, but these errors were encountered: