-
Notifications
You must be signed in to change notification settings - Fork 4
HTTP timeout with repo2data #19
Comments
http timeout is controlled here : https://jupyterhub.readthedocs.io/en/stable/api/spawner.html#spawner |
Using an init container could help to encapsulate repo2data into a separate process (container). |
Maybe it is possible to run an init container for every pod that are building ? |
The issue is that the |
Hopefully the pod used to build the user binder environment has the repo in his annotation, which could be then used as an input for the pod preset (but how?):
|
There is a way to fetch values from a container to store them as env vars. If we store |
Yes it could work |
The issue is how to inject a container (which would run repo2data) to every build pod. |
But |
If we would have controll over binderhub code, we could add it here, maybe it is a room to create a PR (that would fit a general case for them).. |
Or maybe it should be possible to change the |
OK, I thought you were referring to injecting application information into a pod. But you would like to inject a (repo2data) container to a running (build) pod or on pod creation? |
Yep, and for that I need the repository information to pull the |
Example of rendered config for a binder build pod:
|
When data takes to long to download, we got a http timout from the hub pod. We can of course temporally increase the timeout, but this has the advantage to impact restarting time if there is another thing wrong with the environment.
The text was updated successfully, but these errors were encountered: