Open ZazenX opened 3 months ago
@ZazenX Can you locally patch this line?
Maybe
'command': ['marimo', 'edit', '--port', '{port}', '--base-url', os.environ['JUPYTERHUB_SERVICE_PREFIX'] + 'marimo', '--token', '--token-password', token, '--headless', '--host', '0.0.0.0'],
To see if that works? Otherwise you can put a proxy on top and forward traffic
Thank you for investigating this issue. I don't have the capability to work on it myself (not familiar with Kubernetes) but would be happy to incorporate a fix.
@ZazenX Can you locally patch this line?
Maybe
'command': ['marimo', 'edit', '--port', '{port}', '--base-url', os.environ['JUPYTERHUB_SERVICE_PREFIX'] + 'marimo', '--token', '--token-password', token, '--headless', '--host', '0.0.0.0'],
To see if that works? Otherwise you can put a proxy on top and forward traffic
That seemed to do the trick! Cloned the repo and pip install -e
on the singleuser notebook container. My pod logs show all requests to the marimo api work as expected now. I can run code and open files in the jupyter workspace
@ZazenX Could you also test '--host', '127.0.0.1'
?
@akshayka @marimo-team, tagging you in this as dicussed on Discord.
I am having issues deploying Marimo to a k3s cluster. I am able to open the notebook from the launcher, and even pick an existing *.py notebook from the workspace explorer.
Deploying and testing locally on minikube works just fine, I can open marimo from the jupyterlab launcher and write and execute notebooks. When deployed on our k3s cluster on our servers though we run into errors like the ones attached. When the marimo interface opens, I get ConnectionRefusedErrors from the singleuser pod.
Opening files from the jupyter-server-proxy seems to refuse connections from the marimo api.