-
Notifications
You must be signed in to change notification settings - Fork 5
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
FileNotFoundError: [Errno 2] No such file or directory: 'marimo' when attempting to launch Marimo from single-user Docker container #1
Comments
@jyio You may test yourself with b-data's/my demo deployment at https://demo.jupyter.b-data.ch. |
Hey, thank you for trying this out. It looks like it has trouble finding For example, I have this line in my user containers' Dockerfile to allow the single-user JupyterHub to see what the users install: ENV PATH=~/.local/bin:$PATH Later, I could try making a variant that checks |
After setting
and pip install click and clicking on {"detail":"Not Found"} but nothing more in the [container] logs. |
I think this needs more work. With my JupyterLab Julia docker stack, one can simply execute julia -e 'Pkg.add("Pluto")'
pip install jupyter-pluto-proxy restart the server (container) and click on Everything works out of box – thanks to @yuvipanda. Addendum: The following startup files are in place for Julia: https://github.com/b-data/jupyterlab-julia-docker-stack/tree/97fa5731a5272d13261e7f1ece7ee737dd293a31/base/conf/julia/etc/skel/.julia/config |
As suspected, Here's a hack that finds Marimo in the search path prepended with Try this: $ pip install marimo click
$ pip install git+https://github.com/jyio/jupyter-marimo-proxy@user-local-bin After restarting the container and clicking on |
No. Clicking on {"detail":"Not Found"} but nothing more in the [container] logs. |
IMHO Like it is done in But even when providing a properly updated {"detail":"Not Found"} P.S.: It does not work with a non- |
Interesting. Your first post mentions Would you please try Edit: And, I agree that the |
|
No time for further testing. You can use https://demo.jupyter.b-data.ch as test environment. |
Alright, so I set up a minimal JupyterHub with named servers, and |
I did
in a terminal at https://demo.jupyter.b-data.ch/ with Python (jupyterlab/python/scipy:latest) image File / Hub Control Panel > Stop My Server then Start My Server (still with jupyterlab/python/scipy:latest) image) I can see now Marimo icon and run a simple sample Marimo notebook here also |
Thank you @scls19fr for trying the search path hack.
Here's how one might patch
But, if you ask me about properly updating |
Every path outside a user’s home directory: Yes.
Prepending
But even then, it’s complicated:
Really complicated: |
For sure, it's complicated. There are lots of smart folks with strong opinions about what the search path should be, and I'm not one of them 😅 So let's just sort out the issue with the named servers because there's a straightforward solution (let me know if it works for you so we could lay this to rest). And we could keep the special case with the |
With b-data's/my JupyterLab docker stacks (or the demo deployment at https://demo.jupyter.b-data.ch), I recommend pip install marimo click
pip install git+https://github.com/b-data/jupyter-marimo-proxy.git@jupyterlab-docker-stack for now. Then restart the server (container) and click on |
I tried with b-data's/my reference deployment at https://jupyter.b-data.ch, i.e.
After restarting the server (container) and clicking on
Marimo
, I see the following in the logs:Cross reference:
Ping @jyio
The text was updated successfully, but these errors were encountered: