Using xeus-cling kernel in jupyterhub running on kubernetes

[manics]

BinderHub uses repo2docker to build container images that are then run by JupyterHub.

You can configure repo2docker to run a set of commands after every build:

• Using repo2docker — repo2docker 2023.06.0+43.gc6f97e5 documentation
• app — BinderHub documentation

However if your repositories rely on something in your appendix they won’t be compatible with any other BinderHub, so it would be better if you explicitly included xeus-cling in the dependencies for any repository that requires it.

Alternatively if your dependencies are fixed for all notebook repositories you can use nbgitpuller to decouple your dependencies from your notebook repositories, see

Tip: speed up Binder launches by pulling github content in a Binder link with nbgitpuller

Something people often want is to de-couple the content of a repository from the environment that is needed to run it. This would allow you to update the content of a repo without needing to re-build the Binder needed for it. One option is to use a tool called nbgitpuller. This a tool for quickly pulling in GitHub content into a JupyterHub. You can create links that, when clicked, will automatically pull in content into a user’s workspace. nbgitpuller lets you share a link with this structure: …