Support deno lsp in Dev Containers
See original GitHub issueThis would be an enhancement. We would need to investigate how to install Deno in a dev container and what the extension needs to communicate to be able to facilitate that.
I am trying to get deno working inside devcontainers but I am unable to get it to start.
Here is my output, when the deno server is failing to start:
[Error - 9:57:13 PM] Starting client failed
Error: Unsupported server configuration {
"run": {
"command": "",
"args": [
"lsp"
],
"options": {
"env": {
"HOSTNAME": "dbf8ac797c02",
"HOME": "/home/vscode",
"REMOTE_CONTAINERS_IPC": "/tmp/vscode-remote-containers-ipc-35d2f4ce9812147602165fc0d80d74e69c3774eb.sock",
"PATH": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335/bin:/deno/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"VSCODE_AGENT_FOLDER": "/home/vscode/.vscode-server",
"DENO_INSTALL": "/deno",
"DENO_DIR": "/deno/.cache/deno",
"REMOTE_CONTAINERS_SOCKETS": "[\"/home/vscode/.gnupg/S.gpg-agent\"]",
"SHELL": "/bin/bash",
"PWD": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335",
"VSCODE_INJECT_NODE_MODULE_LOOKUP_PATH": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335/remote/node_modules",
"VSCODE_CWD": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335",
"VSCODE_LOG_NATIVE": "false",
"VSCODE_AMD_ENTRYPOINT": "vs/server/remoteExtensionHostProcess",
"VSCODE_PIPE_LOGGING": "true",
"VSCODE_VERBOSE_LOGGING": "true",
"VSCODE_EXTHOST_WILL_SEND_SOCKET": "true",
"VSCODE_HANDLES_UNCAUGHT_ERRORS": "true",
"VSCODE_LOG_STACK": "false",
"VSCODE_NLS_CONFIG": "{\"locale\":\"en\",\"availableLanguages\":{}}",
"REMOTE_CONTAINERS": "true",
"BROWSER": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335/bin/helpers/browser.sh",
"VSCODE_IPC_HOOK_CLI": "/tmp/vscode-ipc-8a221d70-cab1-4faa-86fe-0feace7d2504.sock",
"APPLICATION_INSIGHTS_NO_DIAGNOSTIC_CHANNEL": "true",
"NO_COLOR": true
}
}
},
"debug": {
"command": "",
"args": [
"lsp"
],
"options": {
"env": {
"HOSTNAME": "dbf8ac797c02",
"HOME": "/home/vscode",
"REMOTE_CONTAINERS_IPC": "/tmp/vscode-remote-containers-ipc-35d2f4ce9812147602165fc0d80d74e69c3774eb.sock",
"PATH": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335/bin:/deno/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"VSCODE_AGENT_FOLDER": "/home/vscode/.vscode-server",
"DENO_INSTALL": "/deno",
"DENO_DIR": "/deno/.cache/deno",
"REMOTE_CONTAINERS_SOCKETS": "[\"/home/vscode/.gnupg/S.gpg-agent\"]",
"SHELL": "/bin/bash",
"PWD": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335",
"VSCODE_INJECT_NODE_MODULE_LOOKUP_PATH": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335/remote/node_modules",
"VSCODE_CWD": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335",
"VSCODE_LOG_NATIVE": "false",
"VSCODE_AMD_ENTRYPOINT": "vs/server/remoteExtensionHostProcess",
"VSCODE_PIPE_LOGGING": "true",
"VSCODE_VERBOSE_LOGGING": "true",
"VSCODE_EXTHOST_WILL_SEND_SOCKET": "true",
"VSCODE_HANDLES_UNCAUGHT_ERRORS": "true",
"VSCODE_LOG_STACK": "false",
"VSCODE_NLS_CONFIG": "{\"locale\":\"en\",\"availableLanguages\":{}}",
"REMOTE_CONTAINERS": "true",
"BROWSER": "/vscode/vscode-server/bin/x64/054a9295330880ed74ceaedda236253b4f39a335/bin/helpers/browser.sh",
"VSCODE_IPC_HOOK_CLI": "/tmp/vscode-ipc-8a221d70-cab1-4faa-86fe-0feace7d2504.sock",
"APPLICATION_INSIGHTS_NO_DIAGNOSTIC_CHANNEL": "true",
"NO_COLOR": true
}
}
}
}
at /home/vscode/.vscode-server/extensions/denoland.vscode-deno-3.4.0/client/node_modules/vscode-languageclient/lib/node/main.js:392:35
Dockerfile (untouched default):
FROM mcr.microsoft.com/vscode/devcontainers/base:0-buster
ENV DENO_INSTALL=/deno
RUN mkdir -p /deno \
&& curl -fsSL https://deno.land/x/install/install.sh | sh \
&& chown -R vscode /deno
ENV PATH=${DENO_INSTALL}/bin:${PATH} \
DENO_DIR=${DENO_INSTALL}/.cache/deno
_Originally posted by @lkiii in https://github.com/denoland/vscode_deno/issues/362#issuecomment-841883369_
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Set up your environment | Manual - Deno
Emacs supports Deno via the Deno language server using lsp-mode. Once lsp-mode is installed it should support Deno, which can be configured to...
Read more >Extension Couldn't start client Deno Language Server #362
I am trying to get deno working inside devcontainers but I am unable to get it to start. Here is my output, when...
Read more >How to Resolve LSPs for Deno Projects in Neovim
By creating an empty deno.json file at the root of my Deno projects, the Neovim buffer will make sure that the proper LSP...
Read more >Deno 1.11 Release Notes
The Deno 1.11 release adds new web APIs, resolves long standing ... The LSP now supports per resource configuration as part of the...
Read more >Deno Now Compiles to Self-Contained, Standalone Binaries
LSP defines the protocol used between a code editor or integrated development environment and a language server to provide convenient features ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Or our get default command is broken in the environment. It was designed to make it easier for windows, but hard to say. Either way, we should specifically add the feature and test it instead of leaving it up to chance that it works.
I have been extensively using extension and Deno in dev containers without any issue the past couple weeks. Closing until there is an actionable issue.