SSL certificate problem during repo2docker GitHub Action for building cache for mybinder.org

Binder
,
1

I have set up a repository on GitHub with an environment.yml file and Jupyter notebook .ipynb files that the mybinder org web service is successfully able to pull from and load its contents.

What I tried next was to set up a repo2docker GitHub Action in my repository for automatically building a Docker image and caching it on mybinder org upon every push to the repository. I did so by creating a file /.github/workflows/binder.yml with contents exactly as shown in the Cache builds on mybinder org section of the repo2docker documentation:

name: Binder
on: [push]

jobs:
  Create-MyBinderOrg-Cache:
    runs-on: ubuntu-latest
    steps:
    - name: cache binder build on mybinder.org
      uses: jupyterhub/repo2docker-action@master
      with:
        NO_PUSH: true
        MYBINDERORG_TAG: ${{ github.event.ref }} # This builds the container on mybinder.org with the branch that was pushed on.

However the GitHub workflow fails with the following error message:

Triggering Image Build on mybinder.org
    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                   Dload  Upload   Total   Spent    Left  Speed
  
    0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
    0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  curl: (60) SSL certificate problem: self-signed certificate
  More details here: https://curl.se/docs/sslcerts.html
  
  curl failed to verify the legitimacy of the server and therefore could not
  establish a secure connection to it. To learn more about this situation and
  how to fix it, please visit the webpage mentioned above.

Does anyone here have any idea what exactly is going wrong here, and how I could go about resolving it?

EDIT:

This issue has been cross-posted on StackOverflow and repo2docker-action GitHub (but I’m unable to insert the links here because of an apparent maximum two links per post restriction). At the time of writing replies have not yet been received yet on these other sites.

3

My sincere apologies. A belated list of all the other sites where this issue has been cross-posted is:

4

I note on the Github issue post that you prefaced that with “I’m admittedly not sure this is a bug”.
I suspect it is less a bug and more that it isn’t supported anymore, at least not for the MyBinder use case. (Admittedly, maybe the documentation you reference should get a PR to update it?)
I suspect some of this shift was because the pre-build stuff was written back five or more years ago when there was more big tech company support of the MyBinder federation and DockerHub had yet to implement strong rate limits. I suspect the federation doesn’t want to hit the system with every push now as it is stretched to capacity as things stand.
You can just get in a habit of hitting your launch badge when you have made a non-trivial update or finished a series of atomic updates. You don’t even need to leave that particular browser window open after you trigger the build after a commit. This is what I do & most often things are ready to go if I come back later and want to start a MyBinder-served session from that repo.

Keep in mind that repo2docker is more general than just supporting the MyBinder functionality and so some of the described functionality may work if you had you own BinderHub or were using the repo2docker builds in some other way. If indeed this is the case, as I implied earlier, then the README you reference could probably be fixed up some with someone drafting a PR?