-
Notifications
You must be signed in to change notification settings - Fork 13
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
Running NodeJS server in Docker Container #13
Comments
Try exposing the port |
Any idea how to do it? afaik, this can't be done unless |
I just pushed a new release (1.6.0) of typehole both to npm and to VSCode. Now you are able to configure both the host address the runtime uses to connect to the extension server and the extension HTTP listener port. This is still undocumented, but you can configure the client like this import typehole, { configure } from "typehole";
configure({
extensionHost: 'http:https://host.docker.internal:17341'
}); What comes to your problem: do your docker containers have access to the public internet? One thing you could do is to expose the Typehole port to the outside internet for instance with ngrok.
and then use the address you get in your runtime configuration import typehole, { configure } from "typehole";
configure({
extensionHost: 'https://b8722b82f530.eu.ngrok.io'
}); Could something like this work? |
Closing the issue for now. Please feel free to reopen if you have issues connecting from your code to the extension after upgrading the extension and the runtime. |
I really appreciate your quick response and update. This is very useful, I'm still trying to make it work with my "work" project as there is where I need this the most. The issues I'm facing are very particular to my own specific usecase. I can not use 3rd party servers at all for work, for that reason I'm looking to get Same issue, to use |
typings not working when code is running inside a container. Is there any port I can expose to make it work or some config?
The text was updated successfully, but these errors were encountered: