Closed AngellusMortis closed 5 years ago
Hi @AngellusMortis , I haven't worked with the new extension yet, probably the exec_path and spawn command are calculated and run locally instead of remotely? referenced lines:
A fix could be:
Feel free to fork the project and propose a solution.
Best regards.
calculated and run locally instead of remotely?
I do not think it is. The extension actually gets install inside of the Docker container. It should not know anything about the original host (that is why I have to set the $CODECLIMATE_CODE
because the Code Climate container actually runs on the original host).
It works great with the Remote - SSH variant, it just has an issue with the Remote - Containers variant of the Remote Development stuff.
Feel free to fork the project and propose a solution.
I would love to, but I am not the best with Javascript and I have never used TypeScript.
I managed to figure it out. See #5
Fix merged and published, thanks!
So I am using the new Remote Development feature and I cannot get
linter-codeclimate
to work inside of a Docker container using the Remote - Container extension.How everything is set up:
/var/run/docker.sock
is mounted from my local machine into my docker container.codeclimate
is installed$CODECLIMATE_CODE
set globally in mydocker-compose.yml
to point to the real path to the code.linter-codeclimate
is installed inside of the Docker container (shows up in the Extensions tab and everything)linter_codeclimate.enabled
is set totrue
I am able to do
codeclimate anaylze path/to.py
and it works fine from the integrated terminal, but it will not seem to work from the VS Code extension. I am also not able to find any logs for the extension as well, so I cannot figure out what command it is trying to run or even if it has the correct$CODECLIMATE_CODE
environment variable.I have also verified the extension work perfectly outside of Docker.