Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support different container registry to push and pull #1903

Open
3 tasks
rgaiacs opened this issue Jan 6, 2025 · 0 comments
Open
3 tasks

Support different container registry to push and pull #1903

rgaiacs opened this issue Jan 6, 2025 · 0 comments
Assignees

Comments

@rgaiacs
Copy link
Contributor

rgaiacs commented Jan 6, 2025

Proposed change

In some advanced use cases, the operator might want to push to one container registry and pull from another container registry. For example, the operator want to push to a public container registry like https://hub.docker.com/ and pull from a private proxy cache.

binderhub

This will require

  • Add extra option in Helm chart

    config:
      BinderHub:
        use_registry: true
        image_prefix_to_push: "your-push-registry.io/<prefix>-"
        image_prefix_to_pull: "your-pull0registry.io/<prefix>-"
  • Support new option when building container

  • Support new option when contacting JupyterHub

Who would use this feature?

@arnim and @rgaiacs want to use it at the mybinder.org server operated by GESIS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant