Hello,
I'm trying to connect Lean's Research Docker Jupyter server to VSCode.
Jupyter works properly with the run_docker_notebook.sh script and everything works fine with a browser.
But when I try to connect Jupyter Server to VSCode, the connection fails. I've tried the ip-addresses, which can be found in the Docker logs. When I try the URI http://localhost:8888/lab/workspaces/auto-S, VSCode asks for a username and password for the server, where could these be found?
If someone has experience on this and knows how to connect the Research Notebook to the VSCode using the Docker container, a tutorial on this would be great.
Thank you.
-Lassi Puurunen
Derek Melchin
Hi Lassi,
The Research notebooks are currently only implemented to be run in a browser.
Best,
Derek Melchin
The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
Lassi Puurunen
Thank you Derek.
I got Research Notebook to work in VSCode.
The problem was apparently the command to start the Jupyter Notebook in the QuantConnect / Research docker container,
jupyter lab --ip = '0.0.0.0' --port = 8888 --no-browser --allow-root --notebook-dir = \ "Notebooks \" --LabApp.token = ''
The command specifies that the Jupyter server does not use a token. However, the add-on used by VSCode apparently requires a token to be enabled.
The fix is to change the boot command by removingÂ
--LabApp.token = ''
at the end.
Derek Melchin
Hi Lassi,
Thanks for sharing the solution with the community!
Best,
Derek Melchin
The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
Lassi Puurunen
The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
To unlock posting to the community forums please complete at least 30% of Boot Camp.
You can continue your Boot Camp training progress from the terminal. We hope to see you in the community soon!