# Binder repo stops building: python requires openssl

**URL:** <https://discourse.jupyter.org/t/binder-repo-stops-building-python-requires-openssl/11971>\
**Category:** Binder\
**Created:** [December 1, 2021, 4:44pm UTC](https://discourse.jupyter.org/t/binder-repo-stops-building-python-requires-openssl/11971 "2021-12-01T16:44:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![florian](https://avatars.discourse-cdn.com/v4/letter/f/898d66/32.png) [@florian](https://discourse.jupyter.org/u/florian)\
**Post date:** [December 1, 2021, 4:44pm UTC](https://discourse.jupyter.org/t/binder-repo-stops-building-python-requires-openssl/11971/1 "2021-12-01T16:44:11Z")

</div>

Without any substantial change, the GitLab repo `fkohrt/bachelorarbeit-code` suddenly stopped building on `mybinder.org`. Commit `9c6f208c` ([launch binder](https://mybinder.org/v2/gl/fkohrt%2Fbachelorarbeit-code/9c6f208c?urlpath=rstudio)) has already been built and hence still runs, but the following commit `d0bd23b5` ([launch binder](https://mybinder.org/v2/gl/fkohrt%2Fbachelorarbeit-code/d0bd23b5?urlpath=rstudio)) fails:

> **Build logs**
>
> ```auto
> Waiting for build to start...
> Picked Git content provider.
> Cloning into '/tmp/repo2docker2ek2_wc4'...
> HEAD is now at d0bd23b Fix SPDX copyright text
> Building conda environment for python=Using CondaBuildPack builder
> Building conda environment for python=Building conda environment for python=Step 1/60 : FROM buildpack-deps:bionic
> ---> cb3fc72df6ea
> Step 2/60 : ENV DEBIAN_FRONTEND=noninteractive
> ---> Using cache
> ---> bbf71041feb5
> Step 3/60 : RUN apt-get -qq update && apt-get -qq install --yes --no-install-recommends locales > /dev/null && apt-get -qq purge && apt-get -qq clean && rm -rf /var/lib/apt/lists/*
> ---> Using cache
> ---> 4c3f4df4fe9f
> Step 4/60 : RUN echo "en_US.UTF-8 UTF-8" > /etc/locale.gen && locale-gen
> ---> Using cache
> ---> cf0ddb73b20a
> Step 5/60 : ENV LC_ALL en_US.UTF-8
> ---> Using cache
> ---> e4a48698b2df
> Step 6/60 : ENV LANG en_US.UTF-8
> ---> Using cache
> ---> 219c96346b39
> Step 7/60 : ENV LANGUAGE en_US.UTF-8
> ---> Using cache
> ---> 8ea6f84dfe1b
> Step 8/60 : ENV SHELL /bin/bash
> ---> Using cache
> ---> 519b9e11fdac
> Step 9/60 : ARG NB_USER
> ---> Using cache
> ---> ace306e98486
> Step 10/60 : ARG NB_UID
> ---> Using cache
> ---> e00a45e88442
> Step 11/60 : ENV USER ${NB_USER}
> ---> Using cache
> ---> 386954376551
> Step 12/60 : ENV HOME /home/${NB_USER}
> ---> Using cache
> ---> 379c0e0741d9
> Step 13/60 : RUN groupadd --gid ${NB_UID} ${NB_USER} && useradd --comment "Default user" --create-home --gid ${NB_UID} --no-log-init --shell /bin/bash --uid ${NB_UID} ${NB_USER}
> ---> Using cache
> ---> 7d634b1c860f
> Step 14/60 : RUN apt-get -qq update && apt-get -qq install --yes --no-install-recommends less unzip > /dev/null && apt-get -qq purge && apt-get -qq clean && rm -rf /var/lib/apt/lists/*
> ---> Using cache
> ---> 3a4b31b577c7
> Step 15/60 : EXPOSE 8888
> ---> Using cache
> ---> 9f9275f1ce01
> Step 16/60 : ENV APP_BASE /srv
> ---> Using cache
> ---> 416963c82e96
> Step 17/60 : ENV CONDA_DIR ${APP_BASE}/conda
> ---> Using cache
> ---> 791680a13480
> Step 18/60 : ENV NB_PYTHON_PREFIX ${CONDA_DIR}/envs/notebook
> ---> Using cache
> ---> b1e704210958
> Step 19/60 : ENV NPM_DIR ${APP_BASE}/npm
> ---> Using cache
> ---> 41a53fdedb2f
> Step 20/60 : ENV NPM_CONFIG_GLOBALCONFIG ${NPM_DIR}/npmrc
> ---> Using cache
> ---> e5cd64cb9c34
> Step 21/60 : ENV NB_ENVIRONMENT_FILE /tmp/env/environment.lock
> ---> Using cache
> ---> 9259680e2411
> Step 22/60 : ENV KERNEL_PYTHON_PREFIX ${NB_PYTHON_PREFIX}
> ---> Using cache
> ---> 187cd0243cbc
> Step 23/60 : ENV PATH ${NB_PYTHON_PREFIX}/bin:${CONDA_DIR}/bin:${NPM_DIR}/bin:${PATH}
> ---> Using cache
> ---> 2bf035e29842
> Step 24/60 : COPY --chown=1000:1000 build_script_files/-2fusr-2flib-2fpython3-2e8-2fsite-2dpackages-2frepo2docker-2fbuildpacks-2fconda-2factivate-2dconda-2esh-391af5 /etc/profile.d/activate-conda.sh
> ---> Using cache
> ---> 9ce1f99adb4e
> Step 25/60 : COPY --chown=1000:1000 build_script_files/-2fusr-2flib-2fpython3-2e8-2fsite-2dpackages-2frepo2docker-2fbuildpacks-2fconda-2fenvironment-2elock-1dbdca /tmp/env/environment.lock
> ---> Using cache
> ---> c05ccc6d0ac3
> Step 26/60 : COPY --chown=1000:1000 build_script_files/-2fusr-2flib-2fpython3-2e8-2fsite-2dpackages-2frepo2docker-2fbuildpacks-2fconda-2finstall-2dminiforge-2ebash-514214 /tmp/install-miniforge.bash
> ---> Using cache
> ---> 7e89804a0fe3
> Step 27/60 : RUN TIMEFORMAT='time: %3R' bash -c 'time /tmp/install-miniforge.bash' && rm -rf /tmp/install-miniforge.bash /tmp/env
> ---> Using cache
> ---> 7f77c71775e1
> Step 28/60 : RUN mkdir -p ${NPM_DIR} && chown -R ${NB_USER}:${NB_USER} ${NPM_DIR}
> ---> Using cache
> ---> 14443ad48096
> Step 29/60 : ARG REPO_DIR=${HOME}
> ---> Using cache
> ---> 09630022a293
> Step 30/60 : ENV REPO_DIR ${REPO_DIR}
> ---> Using cache
> ---> d932173aeb30
> Step 31/60 : WORKDIR ${REPO_DIR}
> ---> Using cache
> ---> c9854f1cc8d4
> Step 32/60 : RUN chown ${NB_USER}:${NB_USER} ${REPO_DIR}
> ---> Using cache
> ---> 3908ce93da62
> Step 33/60 : ENV PATH ${HOME}/.local/bin:${REPO_DIR}/.local/bin:${PATH}
> ---> Using cache
> ---> d2e12bf430e9
> Step 34/60 : ENV CONDA_DEFAULT_ENV ${KERNEL_PYTHON_PREFIX}
> ---> Using cache
> ---> 79ce095417df
> Step 35/60 : COPY --chown=1000:1000 src/binder/environment.yml ${REPO_DIR}/binder/environment.yml
> ---> Using cache
> ---> 0c681e0c1be6
> Step 36/60 : USER ${NB_USER}
> ---> Using cache
> ---> 16b562415000
> Step 37/60 : RUN TIMEFORMAT='time: %3R' bash -c 'time mamba env update -p ${NB_PYTHON_PREFIX} -f "binder/environment.yml" && time mamba clean --all -f -y && mamba list -p ${NB_PYTHON_PREFIX} '
> ---> Running in 5d8a96736d33
> 
> Looking for: ['r-base=4.0', 'r-matrixstats=0.59', 'r-tinytex=0.32', 'r-rmarkdown=2.9', 'r-bookdown=0.22', 'pandoc=2.14', 'r-formatr=1.11', 'r-here=1.0.1', 'panflute=2.1.0', 'librsvg=2.50.7', 'r-rsvg=2.1.2', 'r-sysfonts=0.8.3', 'r-showtext=0.9', 'r-ggplot2=3.3.5', 'r-tidyr=1.1.3', 'r-dplyr=1.0.7', 'ghostscript=9.54.0', 'r-rcolorbrewer=1.1_2', 'r-scales=1.1.1', 'r-glue=1.4.2', 'r-rlang=0.4.11', 'r-sf=1.0_1', 'r-png=0.1_7', 'imagemagick=7.1.0_4', 'udunits2=2.2.27.6', 'sqlite=3.36.0', 'geos=3.9.1', 'openssl=1.1.1k', 'libgdal=3.3.1', 'proj=8.0.1', 'r-patchwork=1.1.1', 'r-remotes=2.4.0', 'r-fs=1.5.0', 'r-kableextra=1.3.4', 'r-targets=0.6.0', 'r-withr=2.4.2']
> 
> Encountered problems while solving.
> Problem: package python-3.7.12-hb7a2778_100_cpython requires openssl >=1.1.1l,<1.1.2a, but none of the providers can be installed
> 
> pkgs/main/noarch          
> pkgs/r/linux-64           
> pkgs/r/noarch             
> pkgs/main/linux-64        
> conda-forge/noarch        
> conda-forge/linux-64      
> e[91mtime: 22.492
> e[0mRemoving intermediate container 5d8a96736d33
> The command '/bin/sh -c TIMEFORMAT='time: %3R' bash -c 'time mamba env update -p ${NB_PYTHON_PREFIX} -f "binder/environment.yml" && time mamba clean --all -f -y && mamba list -p ${NB_PYTHON_PREFIX} '' returned a non-zero code: 1Built image, launching...
> Failed to connect to event stream
> 
> ```

It “encountered problems while solving”: `package python-3.7.12-hb7a2778_100_cpython requires openssl >=1.1.1l,<1.1.2a, but none of the providers can be installed`

Building with repo2docker however still works. As there haven’t been any relevant changes to the repository, this must have been caused by some of the underlying software, but I don’t know which. Do you have any ideas?

---

<div class="post-metadata">

**Author:** ![manics](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/manics/32/85_2.png) [@manics](https://discourse.jupyter.org/u/manics)\
**Post date:** [December 1, 2021, 5:03pm UTC](https://discourse.jupyter.org/t/binder-repo-stops-building-python-requires-openssl/11971/2 "2021-12-01T17:03:21Z")

</div>

Can you try running repo2docker locally with no cache, and also pull the latest [base image `buildpack-deps:bionic`](https://github.com/jupyterhub/repo2docker/blob/00769c0fb2624558d600c6a24f14b4ba4154f4ce/repo2docker/buildpacks/base.py#L15)?

Which version of repo2docker are you testing with? Can you see if the problem is reproducible with the latest repo2docker git commit [GitHub - jupyterhub/repo2docker: Turn repositories into Jupyter-enabled Docker images](https://github.com/jupyterhub/repo2docker) ?

Thanks!

---

<div class="post-metadata">

**Author:** ![florian](https://avatars.discourse-cdn.com/v4/letter/f/898d66/32.png) [@florian](https://discourse.jupyter.org/u/florian)\
**Post date:** [December 1, 2021, 5:35pm UTC](https://discourse.jupyter.org/t/binder-repo-stops-building-python-requires-openssl/11971/3 "2021-12-01T17:35:30Z")

</div>

> [@manics](#):
>
> Can you try running repo2docker locally with no cache, and also pull the latest [base image `buildpack-deps:bionic`](https://github.com/jupyterhub/repo2docker/blob/00769c0fb2624558d600c6a24f14b4ba4154f4ce/repo2docker/buildpacks/base.py#L15)?

I have not a lot experience with repo2docker and hence do not know exactly how to change the base image, but what worked was installing Docker CE, repo2docker and building the repository locally:

```bash
curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.sh
pip install jupyter-repo2docker
jupyter-repo2docker https://gitlab.com/fkohrt/bachelorarbeit-code.git

```

> [@manics](#):
>
> Which version of repo2docker are you testing with?

`jupyter-repo2docker --version` leads `2021.08.0`.

> [@manics](#):
>
> Can you see if the problem is reproducible with the latest repo2docker git commit [GitHub - jupyterhub/repo2docker: Turn repositories into Jupyter-enabled Docker images](https://github.com/jupyterhub/repo2docker) ?

Yes, this indeed reproduces with the latest git commit, i.e. after installing repo2docker with

```auto
git clone https://github.com/jupyterhub/repo2docker.git
cd repo2docker
pip install -e .

```

---

<div class="post-metadata">

**Author:** ![florian](https://avatars.discourse-cdn.com/v4/letter/f/898d66/32.png) [@florian](https://discourse.jupyter.org/u/florian)\
**Post date:** [December 16, 2021, 12:07am UTC](https://discourse.jupyter.org/t/binder-repo-stops-building-python-requires-openssl/11971/4 "2021-12-16T00:07:07Z")

</div>

I have created a corresponding issue at GitHub: [Binder repo stops building: python requires openssl · Issue #1101 · jupyterhub/repo2docker · GitHub](https://github.com/jupyterhub/repo2docker/issues/1101)