* Update docker_healthcheck.py
This does not (always) work. Sometimes, other JSON files appear in the directory, like this kernel-xxx file
jpserver-6.json
jpserver-6-open.html
kernel-374f4977-29fc-43e0-8a48-231f6980fdab.json
changing the glob expression to something like "jpserver*.json" instead of simply "*.json" should solve the problem (at least in my case, I checked with a quick patch on a live container, the healthcheck immediately turned 'healthy' again...)
* Update base-notebook/docker_healthcheck.py
* Update docker_healthcheck.py
---------
Co-authored-by: Ayaz Salikhov <mathbunnyru@users.noreply.github.com>
* Get healthcheck URL from JSON file
Obtain Jupyter server's full URL from
/home/$NB_USER/.local/share/jupyter/runtime/*.json
and use it for healthcheck.
* Expand tests for healthcheck
* Update pre-commit config
* Remove workdir from tests
* Wait for container start with 0.1s interval
* Quote NB_USER variable on base-notebook/Dockerfile
* Fix style and make test actually work
* Ooops, GitHub didn't show last line
* Fix mypy
* Use bash with pipefail option for healthcheck
* Create python script for healthcheck
* Don't verify SSL certificate on healthcheck
* Update healthcheck test
- Add "user" parameter
- Add tests when container should not be healthy
* Fix typo
* Update test_healthcheck.py
---------
Co-authored-by: Ayaz Salikhov <mathbunnyru@users.noreply.github.com>
* Add third option: Route container to another local port
Jupyter can have multiple local instances if the used ports don't overlap. Added this as a troubleshooting alternative for users who may want or need to have more than one Jupyter instance running.
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
* Update troubleshooting.md
* Update troubleshooting.md
* Update troubleshooting.md
---------
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Ayaz Salikhov <mathbunnyru@users.noreply.github.com>
