You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the "sticky builds" feature only works when you use a docker-in-docker setup for your BinderHub. This issue is about removing this restriction. See #949 (comment) for some thoughts.
Currently we use the list of DIND pods to find out possible nodes that we can schedule builds on.
In order to remove the restriction that sticky builds only work when DIND is enabled we'd need a new way to find all eligible nodes. Ideally without needing cluster wide privileges.
The text was updated successfully, but these errors were encountered:
Currently the "sticky builds" feature only works when you use a docker-in-docker setup for your BinderHub. This issue is about removing this restriction. See #949 (comment) for some thoughts.
Currently we use the list of DIND pods to find out possible nodes that we can schedule builds on.
In order to remove the restriction that sticky builds only work when DIND is enabled we'd need a new way to find all eligible nodes. Ideally without needing cluster wide privileges.
The text was updated successfully, but these errors were encountered: