Node command not found #9985
Comments
|
Since you already tried: Could you remove all dev containers and make sure you also remove the |
|
I was cleaning up my docker with: docker kill `docker ps -q` && docker rm `docker ps -aq` && docker rmi `docker images -q` -f \
|| true && docker network prune -f \
|| true && docker system prune -af \
|| docker volume ls --format json | jq -r '.Name' | xargs docker volume rmI noted that this I changed this command docker volume ls --format '{{json .Name}}' | jq -rM | xargs docker volume rmNow all my volumes are also been removed. And my devcontainers started to work again!!! |
|
@chrmarti I was able to resolve the But now I'm facing a new bug. The container is starting but devcontainer extension isn't able to connect to the remote container due to this error: Full log: devcontainer-error.log |
|
Another strange thing is, every time I first run the devcontainer, the vscode server starts with the "node" executable... But, if I close it and rerun it, that error So, I cleanup my docker again, reopen the devcontainer to force complete rebuild, and this time (after the container was running) I connected to it to verify the node is running and to verify that the executable was realy there.... and here is the result: root ➜ / $ ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 13:39 ? 00:00:00 /bin/sh -c echo Container started trap "exit 0" 15 exec "$@" while sleep 1 & wait $!; do :; done -
root 34 0 0 13:39 ? 00:00:00 /bin/sh -c echo "New container started. Keep-alive process started." ; export VSCODE_REMOTE_CONTAINERS_SESSION=ba740e01-f868-48ea-aaa6-d2664c202e451718804311593 ; /bin/sh
root 40 34 0 13:39 ? 00:00:00 /bin/sh
vscode 41 0 0 13:39 ? 00:00:00 /bin/sh
root 60 0 0 13:39 ? 00:00:00 /bin/sh
vscode 189 0 0 13:39 ? 00:00:00 /bin/sh
vscode 248 189 0 13:39 ? 00:00:00 /home/vscode/.vscode-server/bin/611f9bfce64f25108829dd295f54a6894e87339d/node /tmp/vscode-remote-containers-server-7d758ceb-5491-468a-8535-cad53eed9d6a.js
vscode 255 0 0 13:39 ? 00:00:00 sh /home/vscode/.vscode-server/bin/611f9bfce64f25108829dd295f54a6894e87339d/bin/code-server --log debug --force-disable-user-env --server-data-dir /home/vscode/.vscode-server --use-host-
vscode 268 255 42 13:39 ? 00:00:13 /vscode/vscode-server/bin/linux-x64/611f9bfce64f25108829dd295f54a6894e87339d/node /vscode/vscode-server/bin/linux-x64/611f9bfce64f25108829dd295f54a6894e87339d/out/server-main.js --log de
vscode 360 268 0 13:39 ? 00:00:00 /vscode/vscode-server/bin/linux-x64/611f9bfce64f25108829dd295f54a6894e87339d/node /vscode/vscode-server/bin/linux-x64/611f9bfce64f25108829dd295f54a6894e87339d/out/bootstrap-fork --type=p
root 504 0 0 13:40 pts/0 00:00:00 /bin/bash
root 539 1 0 13:40 ? 00:00:00 sleep 1
root 540 504 0 13:40 pts/0 00:00:00 ps -ef
root ➜ / $ /home/vscode/.vscode-server/bin/611f9bfce64f25108829dd295f54a6894e87339d/node
bash: /home/vscode/.vscode-server/bin/611f9bfce64f25108829dd295f54a6894e87339d/node: No such file or directoryNote that, the "vscode server node process" is running, but if I try to run the node command alone it fails with |
|
I finally discovered the ofensor. My company has installed an anti virus app (Microsoft Sentinel One). It agent was deleting the container volume files. In agent logs I was able to identify the issue: This AV agent hasn't a ui interface to report issues, I just has suspected about "and if the problem wasn't the extension but yes another app". So I collected the agent logs and "skadush", that was it! Sorry about spend your time. |
VSCode Version: 1.90.1
Local OS Version: 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 GNU/Linux
Remote OS Version: mcr.microsoft.com/devcontainers/dotnet:1-8.0-bookworm
Remote Extension/Connection Type: Containers/WSL/Server
Logs:
Steps to Reproduce:
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
I tried to clean all my docker images, networks, volumes, etc... and start a new vscode profile with only the devcontainer extension, but the problems continues.
The text was updated successfully, but these errors were encountered: