I have a kernel starter in a container. I have its connection_file.json.

If I try to connect Jupiter server inside the same container, everything works fine.

jupyverse --set kernels.allow_external_kernels=true --set kernels.external_connection_dir=connection_folder --open-browser

But if I do it on the host, an error pops up.

File ".venv/lib/python3.12/site-packages/fps_kernels/routes.py", line 185, in create_session
    kernel_name = kernels[kernel_id]["name"]
                  ~~~~~~~^^^^^^^^^^^
KeyError: 'f1c2e279-2f5f-4b14-a65f-b981f89b4220'

In this case, Jupiter sees a new kernel connection. But it does not see the kernel itself.

In this regard, I have questions

1. What else should be given to the host, in addition to the connect_file?
2. Is it possible to do this at all? Or should jupyter_server be located next to the kernel?