Open PoslavskySV opened 4 years ago
MacOS Catalina 10.15.1 EKS/Kubernetes 1.15 JupyterHub 0.9.0 Almond 0.9.1
Hi,
I had a similar issue where I couldn't use the image in JupyterHub running on Kubernetes (EKS cluster). The kernel wouldn't show up in the list as OP says.
After some investigation, I realized that Almond kernel files are installed inside $HOME. Since JupyterHub's KubeSpawner mounts a volume at $HOME in the container, the kernel files are not visible to Jupyter notebook.
A possible workaround is to run ./almond --global ...
while building the image, which results in the kernel getting installed at /usr/local/share/jupyter/
.
Thx!
@tusharm Thanks for the workaround!
@alexarchambault we just ran into the same problem. Would it be possible to write almond to a different directory by default? If so, shall I create a PR for it?
It seams like this issue is fixed. when I reproduce the steps by @PoslavskySV :
$ jupyter kernelspec list
Available kernels:
scala212 /home/jovyan/.local/share/jupyter/kernels/scala212
scala213 /home/jovyan/.local/share/jupyter/kernels/scala213
scala32 /home/jovyan/.local/share/jupyter/kernels/scala32
python3 /opt/conda/share/jupyter/kernels/python3
Hi,
I've created simple k8s pod with almond jupyter:
so it can be accessible with port forwarding:
However, container is always failed to start with the following error:
OK... Specifying security context in pod
spec
:I am able to make it running. But then when connecting to Jupyter, there is no Scala kernel installed there, just only Python 3:
One can check it directly login into pod:
Can you please help?
Thanks!