[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3759: The CircleCI Dockerhub authorization context prevents contributions from GitHub.com forked repositories from running

[Tahoe-LAFS]

#3759: The CircleCI Dockerhub authorization context prevents contributions from
GitHub.com forked repositories from running
-------------------------+-----------------------
     Reporter:  exarkun  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  n/a
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------

Comment (by sajith):

 CircleCI's UI is something of a mystery here. It simply says that PR 1100
 is
 "unauthorized", but not exactly what is unauthorized, why, and how we can
 solve the problem.

 [[https://app.circleci.com/pipelines/github/tahoe-lafs/tahoe-
 lafs/2736/workflows/129fc5de-39a9-45f1-b6fe-ba9942ac1cea|This]] is a
 problematic CI run.  For a "normal" run, the first thing to run on
 CircleCI is the "spin up the environment" step, where a Docker image is
 pulled, as in [[https://app.circleci.com/pipelines/github/tahoe-lafs
 /tahoe-lafs/2735/workflows/41cfda6c-2c6c-4de2-902b-
 b15afdf6e573/jobs/57280|this example]]. But in the case of PR 1100, it
 doesn't seem that any attempt has been made to pull an image from Docker
 Hub.

 This CircleCI forum post looks relevant: [[https://discuss.circleci.com/t
 /how-do-i-know-why-a-build-is-unauthorized/36538|"How do I know _why_ a
 build is unauthorized?"]].

 So does this article: [[https://support.circleci.com/hc/en-
 us/articles/360050273651-Builds-Unauthorized-due-to-contexts|"Builds
 "Unauthorized" due to contexts"]].

 (Further, per an update on a CircleCI forum post from September 2020
 ([[https://discuss.circleci.com/t/updated-authenticate-with-docker-to-
 avoid-impact-of-nov-1st-rate-limits/37567|"Authenticate with Docker to
 avoid impact of Nov. 1st rate limits"]]), "CircleCI has partnered with
 Docker to ensure that our users can continue to access Docker Hub without
 rate limits. On November 1st, with few exceptions, you should not be
 impacted by any rate limits when pulling images from Docker Hub through
 CircleCI". It looks like Docker Hub login is not mandatory for pulling
 images.)

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3759#comment:1>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage