Skip to content
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

Error when running initializeCommand on Windows #2442

Closed
sbatten opened this issue Feb 26, 2020 · 1 comment
Closed

Error when running initializeCommand on Windows #2442

sbatten opened this issue Feb 26, 2020 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers verified Verification succeeded
Milestone

Comments

@sbatten
Copy link
Member

sbatten commented Feb 26, 2020

refs #2407

[3497 ms] Repository 'sbatten/vscode-remote-try-node.git' was already cloned into '/workspaces/vscode-remote-try-node'.

[3497 ms] Start: Run in container: cat /workspaces/vscode-remote-try-node/.devcontainer/devcontainer.json 2>/dev/null
[3501 ms] Start: Run: docker exec -w /workspaces/vscode-remote-try-node -u root a7a68c6bd8f5e333faa3a94cbd15100337afff38c07836e82877ca389b0825f5 /bin/sh -c echo 'THIS IS THE INITIAL COMMAND OUTPUT'
[3827 ms] 
[4121 ms] THIS IS THE INITIAL COMMAND OUTPUT

[4151 ms] Start: Run: /bin/sh -c echo 'THIS IS THE INITIAL COMMAND OUTPUT'
[4164 ms] Error: File not found:
at new WindowsPtyAgent (c:\<obfuscated>\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\node_modules.asar\node-pty\lib\windowsPtyAgent.js:77:36)
@chrmarti chrmarti added bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers labels Feb 27, 2020
@chrmarti chrmarti added this to the February 2020 milestone Feb 27, 2020
@JacksonKearl JacksonKearl added the verified Verification succeeded label Feb 28, 2020
@JacksonKearl
Copy link
Contributor

Verified by #2407 (comment)

@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants