Failure to update description on DockerHub through CI

[zigarn]

Build 438 on April 29th, 2022 at 11:53:01 AM GMT+02:00 was OK.
Next build 444 on June 15th, 2022 at 3:08:14 PM GMT+02:00 was NOK.
Nothing changed in term of CI between those 2: abd3faf...91d6c92

Issue is in updating description on DockerHub.
Done with command from orb circleci/docker: https://circleci.com/developer/orbs/orb/circleci/docker#commands-update-description

When debugging:

curl -s -o /dev/null -w '%{http_code}' -X PATCH --data-urlencode full_description@./README.md https://hub.docker.com/v2/repositories/zenika/sensei-test/
# {"detail": "access is forbidden with a JWT issued from a personal access token"}

I would guess the CircleCI context docker-hub-zenika was changed to use a Personnal Access Token instead of password and/or 2FA was activated for this account, which break API calls...
https://docs.docker.com/docker-hub/api/latest/#tag/authentication:

[zigarn]

Looks like an issue on DockerHub side: docker/hub-feedback#2127 (comment)

[zigarn]

2 fast workarounds available:

• Disable update-description in CI
• Set DOCKERHUB_PASS in CircleCI context of org Zenika back to the dsizenika password (like for the same in Zenika-Training org)

WDYT @hgwood?

[hgwood]

I would guess the CircleCI context docker-hub-zenika was changed to use a Personnal Access Token instead of password and/or 2FA was activated for this account, which break API calls...

Both!

Disabling 2FA is not an option IMO. Disabling update-description seems better to me.

[zigarn]

I'll do some more tests. At first quick check it was working so it's weird.
Also waiting a bit for DockerHub to fix issue on their side is an option if we don't care to have failing build on main until then.

[hgwood]

Yes it seems very weird that the API wouldn't accept access tokens. Aren't they made exactly for this?

[zigarn]

From docker/hub-feedback#2127 (comment) it's an issue that may be fixed soon.

[zigarn]

Now hitting CircleCI-Public/docker-orb#138