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
Attempt to fix #4315, practically by using extraVolumes and extraVolumeMounts config introduced from 2i2c-org/binderhub-service#122, in order to mount the k8s Secret created by the binderhub-service chart when configuring buildPodsRegistryCredentials.
The name of the secret to mount should be named something like small-binder-binderhub-service-build-pods-docker-config, and you can configure the location it was mounted to be detected by binderhub via binderhub-service.config.DockerRegistry.docker_config_path.
Testing of this can be done in opensci's small binderhub, where its verified by building a repo twice and the second time it doesn't do a build at all but just launches, after success, we should update all hubs using quay.io in the same way.
The text was updated successfully, but these errors were encountered:
Attempt to fix #4315, practically by using
extraVolumes
andextraVolumeMounts
config introduced from 2i2c-org/binderhub-service#122, in order to mount the k8s Secret created by the binderhub-service chart when configuringbuildPodsRegistryCredentials
.The name of the secret to mount should be named something like
small-binder-binderhub-service-build-pods-docker-config
, and you can configure the location it was mounted to be detected by binderhub viabinderhub-service.config.DockerRegistry.docker_config_path
.Testing of this can be done in opensci's small binderhub, where its verified by building a repo twice and the second time it doesn't do a build at all but just launches, after success, we should update all hubs using quay.io in the same way.
The text was updated successfully, but these errors were encountered: