GESIS node fail to launch repository

[rgaiacs]

When building a new repository commit,

Successfully built ccb5723cecd5
Successfully tagged gesiscss/binder-r2d-g5b5b759-gesiscss-2dorc2-2dtest-2dbuild-ced273:01429fa5102ba6035419cf9bad2e04157bcc4391
Error during build: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out.

Is this UnixHTTPConnectionPool related to push the image?

List of Related Material

• https://discourse.jupyter.org/t/i-get-read-timed-out-errors-on-when-pushing-image-ovh/1394/3

  Similar problem with OVH in 2019. "Resolved" (?) with different docker registry for the OVH cluster.

• Configurable docker push timeout repo2docker#711

  Upstream issue at repo2docker.

• r2d-action broken? 2i2c-org/utoronto-image#20

  Similar issue from https://github.com/jupyterhub/repo2docker-action

• Allow passing in extra args to Docker initialization repo2docker#1124

  Pull request to repo2docker

[arnim]

Still wandering if we could mitigate these if we had an on prem container registry with pass through

[arnim]

To allow any training workshop where students can build their own binders (e.g., https://bit.ly/WfRRwRGit) we need to support at least 30 concurrent builds. This is fare from what the docker Hub API rate limitations currently allow us to do.

[rgaiacs]

A workaround to try is to extend the allowed time as suggested in docker/compose#3927 (comment)

[rgaiacs]

docker/docker-py#398 suggests that the problem is overloading GESIS machine.