Simon Li

I think we need to bump the version of `docker`(-py) too, otherwise we'll hit https://github.com/docker/docker-py/issues/3256

Can you show us your latest full configuration and customisations? Perhaps it's related to the dynamic credentials discussed in https://github.com/jupyterhub/binderhub/issues/1934

[docker-py has been updated](https://pypi.org/project/docker/7.1.0/), but an old version is cached in GitHub actions resulting in some failures.

@dependabot merge

Can you turn on JupyterHub debug logging, and show us the full logs starting from when the hub shutdown is requested?

Thanks! The spawner was stopped: ``` [C 2025-09-26 09:29:23.875 ServerApp] received signal 15, stopping [C 2025-09-26 09:29:23.875 JupyterHub app:3861] Received signal SIGTERM, initiating shutdown... [I 2025-09-26 09:29:23.876 JupyterHub app:3465] Cleaning...

To help narrow this down could you try without ProfilesSpawner, so only the LocalProcessSpawner is configured? If it's not reproducible, then add ProfilesSpawner back with just a single profile.

Do you have the same problem if you run and shutdown JupyterLab directly without JupyterHub?

It's not required, I just thought it'd help modernise things and avoid confusion over why we need both pyproject.toml and setup.py. I'm happy to leave things as they are.

That's usually a configuration error that needs to be fixed by the JupyterHub admin: https://jupyterhub.readthedocs.io/en/stable/faq/troubleshooting.html#i-m-seeing-403-forbidden-xsrf-cookie-does-not-match-post-when-users-try-to-login Do you have an example of when it occurs for some other reason?