Jeremy Tuloup

@martinRenou curious to know if there are any blockers that would prevent moving to mambajs? If mambajs is used to do the environment solving in the lite addon, does that...

The upstream change was reverted: https://github.com/jupyter/nbformat/pull/397 So maybe this will be fixed when there is a new release of `nbformat`.

Not sure. Maybe updating the version of `dockerspawner` used here may help? https://github.com/plasmabio/plasma/blob/1f8376231a693a01d466e273091a0afcf725b60f/tljh-plasma/setup.py#L9

Or maybe try to update `dockerspawner` manually to first see if that fixes the issue?

Some notes. The `tljh-repo2docker` plugin seems to be accessing `ContainerConfig` here: https://github.com/plasmabio/tljh-repo2docker/blob/e1d92a94a0ae72266a98cfb99dbd2f7461606075/tljh_repo2docker/__init__.py#L137 Also there are two new versions of `dockerspawner` available, one of them includes a security fix: https://jupyterhub-dockerspawner.readthedocs.io/en/latest/changelog.html

Ah, looks like https://github.com/plasmabio/tljh-repo2docker/pull/103 and related link may be relevant: https://docs.docker.com/engine/deprecated/#container-and-containerconfig-fields-in-image-inspect 

@pierrepo curious if you still have the server / environment where this error happens. If so, maybe it could be worth trying the patch from https://github.com/plasmabio/tljh-repo2docker/pull/103 by manually modifying the...

For reference, installing `jupyterlab=4.2.5` and `jupyter-collaboration=3` together in a clean environment and then creating a *new* notebook seems to be working fine: 

Maybe one these two extensions would work with JupyterLite? - https://github.com/jupyterlab-contrib/rise - https://github.com/deathbeds/jupyterlab-deck

> it could be caused by [jupyterlab/jupyterlab#15958](https://github.com/jupyterlab/jupyterlab/pull/15958), and I checked that it is indeed the case. How did you check? The same PR seems to be causing issues with other...