@@ -355,7 +355,7 @@ You now have a functioning BinderHub at the above IP address.
355355Customizing your Deployment
356356---------------------------
357357
358- The Helm chart used to install your BinderHub deployemnt exposes a number of
358+ The Helm chart used to install your BinderHub deployment exposes a number of
359359optional features. Below we describe a few of the most common customizations
360360and how you can configure them.
361361
@@ -431,7 +431,7 @@ time at `the token administration page <https://github.com/settings/tokens>`_.
431431 GitLab
432432^^^^^^
433433
434- To access private GitLab repos, create an API token for your binderhub user
434+ To access private GitLab repos, create an API token for your BinderHub user
435435under "User Settings" > "Access tokens". It at least needs the scopes "api" and
436436"read_repository".
437437
@@ -452,20 +452,20 @@ clone a repo.
452452Use Docker-inside-Docker (DinD)
453453~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
454454
455- By default, BinderHub will build pods with the host Docker installation.
455+ By default, BinderHub will build images with the host Docker installation.
456456This often means you are stuck with whatever version of Docker provided by your
457457cloud provider. BinderHub supports an alternative that uses `Docker-in-Docker
458458(DinD) <https://hub.docker.com/_/docker> `_. To turn `dind ` on, you'll need to set
459459the following configuration in your ``config.yaml `` file::
460460
461+ imageBuilderType: dind
461462 dind:
462- enabled: true
463463 daemonset:
464464 image:
465465 name: docker
466466 tag: 18.09.2-dind
467467
468- If you plan to host multiple BinderHub deployments on the same kubernetes
468+ If you plan to host multiple BinderHub deployments on the same Kubernetes
469469cluster, you'll also need to isolate the host socket and library directory
470470for each DinD application::
471471
@@ -474,4 +474,32 @@ for each DinD application::
474474 hostSocketDir: /var/run/dind/"<name of deployment, e.g. staging>"
475475
476476
477+ Use Podman-inside-Kubernetes (PinK)
478+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
479+
480+ In case Docker is not an option, Podman can be used as drop in replacement.
481+ Note that the implications about using a host installation of Podman are the same
482+ as with Docker. BinderHub supports an alternative that uses `Podman-in-Kubernetes
483+ (PinK) <https://www.redhat.com/sysadmin/podman-inside-kubernetes> `_. To turn
484+ `pink ` on, you'll need to set the following configuration in your ``config.yaml `` file::
485+
486+ imageBuilderType: pink
487+
488+ You can optionally override the default podman image:
489+
490+ pink:
491+ daemonset:
492+ image:
493+ name: quay.io/podman/stable
494+ tag: v4.2.0
495+
496+ If you plan to host multiple BinderHub deployments on the same Kubernetes
497+ cluster, you'll also need to isolate the host socket and library directory
498+ for each DinD application::
499+
500+ pink:
501+ hostStorageDir: /var/lib/pink/"<name of deployment, e.g. staging>"
502+ hostSocketDir: /var/run/pink/"<name of deployment, e.g. staging>"
503+
504+
477505For next steps, see :doc: `../debug ` and :doc: `turn-off `.
0 commit comments