"Launch attempt failed" with no further details

[hannorein]

Bug description

Binder instance files to load.

How to reproduce

When trying to launch a binder instance of the rebound repository, it fails with the following log:

Found built image, launching...
Launching server...
Server requested
2023-09-25T23:29:54.610300Z [Normal] Successfully assigned ovh2/jupyter-hannorein-2drebound-2d7j0pxohv to user-202211a-node-198ed1
2023-09-25T23:29:55Z [Normal] Container image "jupyterhub/mybinder.org-tc-init:2020.12.4-0.dev.git.4289.h140cef52" already present on machine
2023-09-25T23:29:55Z [Normal] Created container tc-init
2023-09-25T23:29:55Z [Normal] Started container tc-init
2023-09-25T23:29:57Z [Normal] Pulling image "2lmrrh8f.gra7.container-registry.ovh.net/mybinder-builds/r2d-g5b5b759hannorein-2drebound-d27a14:ca085f96e42f0bf32b1ee685ec66bb648b1adc35"
Launch attempt 1 failed, retrying...
Server requested
2023-09-25T23:32:43.933479Z [Normal] Successfully assigned ovh2/jupyter-hannorein-2drebound-2dsf9m0olm to user-202211a-node-198ed1
2023-09-25T23:32:44Z [Normal] Container image "jupyterhub/mybinder.org-tc-init:2020.12.4-0.dev.git.4289.h140cef52" already present on machine
2023-09-25T23:32:44Z [Normal] Created container tc-init
2023-09-25T23:32:45Z [Normal] Started container tc-init
2023-09-25T23:32:47Z [Normal] Pulling image "2lmrrh8f.gra7.container-registry.ovh.net/mybinder-builds/r2d-g5b5b759hannorein-2drebound-d27a14:ca085f96e42f0bf32b1ee685ec66bb648b1adc35"

There is no real error message besides "launch attempt failed" so I'm not sure how to further debug it.

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[TomWinder]

I am experiencing this same issue. Builds proceed normally, but then repeatedly stalls at the point of launching (across Chrome, Chrome Incognito, Firefox, Safari -- proceeding from the pre-built image). E.g. output pasted below.

Found built image, launching...
Launching server...
Server requested
2023-09-27T23:49:14.326784Z [Normal] Successfully assigned ovh2/jupyter-tomwinder-2dquakemigrate-2d95u7jpc8 to user-202211a-node-955bd6
2023-09-27T23:49:15Z [Normal] Container image "jupyterhub/mybinder.org-tc-init:2020.12.4-0.dev.git.4289.h140cef52" already present on machine
2023-09-27T23:49:15Z [Normal] Created container tc-init
2023-09-27T23:49:15Z [Normal] Started container tc-init
2023-09-27T23:49:17Z [Normal] Pulling image "2lmrrh8f.gra7.container-registry.ovh.net/mybinder-builds/r2d-g5b5b759tomwinder-2dquakemigrate-8be9d9:baa136a76197b72be3c57fa9cf569abab059a7fd"
Launch attempt 1 failed, retrying...
Server requested
2023-09-27T23:52:22.501717Z [Normal] Successfully assigned ovh2/jupyter-tomwinder-2dquakemigrate-2d0yxmgwaj to user-202211a-node-955bd6
2023-09-27T23:52:23Z [Normal] Container image "jupyterhub/mybinder.org-tc-init:2020.12.4-0.dev.git.4289.h140cef52" already present on machine
2023-09-27T23:52:23Z [Normal] Created container tc-init
2023-09-27T23:52:23Z [Normal] Started container tc-init
2023-09-27T23:52:24Z [Normal] Pulling image "2lmrrh8f.gra7.container-registry.ovh.net/mybinder-builds/r2d-g5b5b759tomwinder-2dquakemigrate-8be9d9:baa136a76197b72be3c57fa9cf569abab059a7fd"
Spawn failed: pod ovh2/jupyter-tomwinder-2dquakemigrate-2d0yxmgwaj did not start in 300 seconds!
Launch attempt 2 failed, retrying...
Server requested
2023-09-28T00:01:25.097160Z [Normal] Successfully assigned ovh2/jupyter-tomwinder-2dquakemigrate-2dz4texn84 to user-202211a-node-955bd6
2023-09-28T00:01:26Z [Normal] Container image "jupyterhub/mybinder.org-tc-init:2020.12.4-0.dev.git.4289.h140cef52" already present on machine
2023-09-28T00:01:26Z [Normal] Created container tc-init
2023-09-28T00:01:26Z [Normal] Started container tc-init
2023-09-28T00:01:26Z [Normal] Pulling image "2lmrrh8f.gra7.container-registry.ovh.net/mybinder-builds/r2d-g5b5b759tomwinder-2dquakemigrate-8be9d9:baa136a76197b72be3c57fa9cf569abab059a7fd"
Launch attempt 3 failed, retrying...
Server requested
2023-09-28T00:03:09.993254Z [Normal] Successfully assigned ovh2/jupyter-tomwinder-2dquakemigrate-2d5xar1d59 to user-202211a-node-955bd6
2023-09-28T00:03:10Z [Normal] Container image "jupyterhub/mybinder.org-tc-init:2020.12.4-0.dev.git.4289.h140cef52" already present on machine
2023-09-28T00:03:10Z [Normal] Created container tc-init
2023-09-28T00:03:11Z [Normal] Started container tc-init
2023-09-28T00:03:12Z [Normal] Pulling image "2lmrrh8f.gra7.container-registry.ovh.net/mybinder-builds/r2d-g5b5b759tomwinder-2dquakemigrate-8be9d9:baa136a76197b72be3c57fa9cf569abab059a7fd"

I haven't sat through more than 3 failed attempts (over ~ 30 minutes) before giving up and killing the tab. Some that I have left sitting in the background have eventually launched the lab interface after more than 45 minutes. I have never experienced such terribly slow loading before on binder.

---

Edit: this died a few minutes later with the additonal two lines:

Spawn failed: pod ovh2/jupyter-tomwinder-2dquakemigrate-2d5xar1d59 did not start in 300 seconds!
Spawn failed: pod ovh2/jupyter-tomwinder-2dquakemigrate-2d5xar1d59 did not start in 300 seconds!

And reverted to the message "Failed. Try refreshing this page in a few seconds." in the loading bar.

---

However, when I'm lucky enough to be directed to a "gesis" hub instead of jupyter, the notebook launches within a minute. E.g. output here:

Found built image, launching...
Launching server...
Server requested
2023-09-28T00:06:45.966292Z [Normal] Successfully assigned gesis/jupyter-tomwinder-2dquakemigrate-2db62qhacf to spko-css-app03
2023-09-28T00:06:46Z [Normal] Container image "jupyterhub/k8s-network-tools:3.0.0-beta.3" already present on machine
2023-09-28T00:06:46Z [Normal] Created container block-cloud-metadata
2023-09-28T00:06:46Z [Normal] Started container block-cloud-metadata
2023-09-28T00:06:47Z [Normal] Container image "gesiscss/binder-r2d-g5b5b759-tomwinder-2dquakemigrate-8be9d9:baa136a76197b72be3c57fa9cf569abab059a7fd" already present on machine
2023-09-28T00:06:47Z [Normal] Created container notebook
2023-09-28T00:06:48Z [Normal] Started container notebook

To reproduce: launch https://mybinder.org/v2/gh/TomWinder/QuakeMigrate/prac_v1?labpath=examples%2FVolcanotectonic_Iceland_prac%2FQM_prac.ipynb , and wait.

[TomWinder]

Seems like it is still related to this:

• https://discourse.jupyter.org/t/unable-to-launch-jupyter-on-binder/19102/14
• https://discourse.jupyter.org/t/first-time-user-unable-to-launch-jupyter4kids-binder/19213

First link contains a workaround (pasted below) that worked for me. But not straightforward to share (if you e.g. previously used binder to host software demo or teaching resources.....)

It built in a very reasonable time and launched by going here 14 and entering your repo https://github.com/mettalrose/DS2F_Workshop_Text_Mining in the top line of the form and clicking on the launch button.

---

EDIT: GESIS FAQ provides support for shareable links - see bottom of this page: https://notebooks.gesis.org/faq.html

How can I create a direct launch link for my notebooks?

Just like mybinder.org, you can create a direct launch link for a notebook repository. To launch the notebook without persistence (no login required) you can create a URL like https://notebooks.gesis.org/binder/v2/gh/github_account_name/repository_name/HEAD with appropriate 'github_account_name' and 'repository_name'. To launch this with persistence (login required) you can construct a URL with https://notebooks.gesis.org/services/binder/v2/gh/github_account_name/repository_name/HEAD.

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[yosh-matsuda]

Same here in my hosted BinderHub. I found a workaround by adding the following to environment.yml.

dependencies:
  - traitlets<5.10.0

This problem may be related to jupyter/notebook#7048 ; notebook < 6.5.6 does not work with traitlets >= 5.10 but conda provides notebook v6.3.0.