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.

Sign up for GitHub

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

A small docs update #945

Merged
merged 2 commits into from
Sep 8, 2019
Merged

A small docs update #945

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b0ef4dd
use same capitalisation for Git everywhere
nuest Sep 7, 2019
fbbc302
restructure references to next step, closes #902
nuest Sep 7, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
restructure references to next step, closes #902
  • Loading branch information
@nuest
nuest committed Sep 7, 2019
commit fbbc302b7f4153add3d6d3372e65e85e75e7f93c
15 changes: 5 additions & 10 deletions doc/setup-registry.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,16 +6,16 @@ Set up the container registry
BinderHub will build Docker images out of Git repositories, and then push
them to a Docker registry so that JupyterHub can launch user servers based
on these images. You can use any registry that
you like, though this guide covers how to properly configure two popular
registries: the **Google Container Registry** (``gcr.io``) and DockerHub
(``hub.docker.com``).
you like, though this guide covers how to properly configure several popular
registries. The next step, :doc:`setup-binderhub`, explains how you can
properly configure BinderHub to use one of these registries.

.. _use-gcr:

Set up Google Container Registry
--------------------------------

To use Google Container Registry, you'll need to provide BinderHub
To use Google Container Registry (``gcr.io``), you'll need to provide BinderHub
with proper credentials so it can push images. You can do so by creating a
service account that has authorization to push to Google Container Registry:

Expand Down Expand Up @@ -48,7 +48,7 @@ registry.
Set up Docker Hub registry
------------------------------

To use **Docker Hub** as a registry first you have to create a
To use **Docker Hub** (``hub.docker.com``) as a registry first you have to create a
`Docker ID account <https://docs.docker.com/docker-id/>`_
in `Docker Hub <https://hub.docker.com/>`_. Your
Docker ID (username) and password are used to push Docker images to the registry.
Expand All @@ -57,9 +57,6 @@ If you want to store Docker images under an organization, you can
`create an organization <https://docs.docker.com/docker-hub/orgs/>`_.
This is useful if different Binder instances want to use same registry to store images.

See the next section for how to properly configure your BinderHub to use
Docker Hub.

.. _use-acr:

Set up Azure Container Registry
Expand Down Expand Up @@ -140,8 +137,6 @@ where:
SERVICE_PRINCIPAL_PASSWORD=$(az ad sp create-for-rbac --name <SP_NAME> --role AcrPush --scopes <ACR_ID> --query password --output tsv)
SERVICE_PRINCIPAL_ID=$(az ad sp show --id http://<SP_NAME> --query appId --output tsv)

See the next section for how to properly configure your BinderHub to use Azure Container Registry.

Next step
---------

Expand Down