This repository has been archived by the owner on Oct 5, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 346
Jupyter notebook on theia-python running on internal domain #429
Labels
Comments
Thanks @mridup for trying this and sharing your results. I see a few exceptions in the FWIW, I also get a
This one looks related to
|
The first exception might have been fixed upstream a couple of months ago: microsoft/vscode-python#13839 |
the above of course then goes on to trigger the "Syntax Error: Invalid or unexpected token" error we see in the console. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
following #423 :
we were able to correctly deploy theia-python docker on an Azure ACI instance with letsencrypt certificate and have the webviews and jupyter notebooks working correctly.
Further we deployed the theia-python docker on an internal domain with it's own CA certificate issued by internal Root CA.
So this domain cannot be reached from outside and also there is no outside connectivity from this host (except can be configured by corporate proxy of course).
So we solved the issue of web workers not running without SSL and also by configuring the THEIA_WEBVIEW_EXTERNAL_ENDPOINT as {{hostname}}
But now in the internal server, we are again not able to run jupyter notebook. There is no error related to webviews or web workers now and hence the previous issue in #423 is not the concern here.
The notebook tab does open but there is no rendering of the notebook cells etc. There is only one indication but not sure if it is related.
When the notebook is opened the output on browser console is the following:
Also in the docker logs there is a lot less logs output (expecially related to 'Python Extension') compared to the working case on Azure ACI. The logs does not indicate any direct reference to any error related to the python notebook.
To note here is that the images used for the internal server and Azure ACI are exactly the same except that the certificates and key are different in both cases.
Another difference is that the internal server container runs as root wherease the Azure ACI container runs as USER 'theia'. although this shouldn't make any difference.
Here are the docker logs from internal server domain when a python notebook is opened (does not work):
internal_server_logs.txt
And here are the docker logs from Azure ACI when a python notebook is opened (works):
azure_aci.txt
any pointers would be super helpful!
The text was updated successfully, but these errors were encountered: