This new Docker issue has come up more than a few times in more than a few open source places. It was my understanding that the LF was trying to work with Docker to solve this for all of their open source projects, inclusive of LFN/FD.io. If that doesn’t happen then, to Dave’s point, fdiotools will have to go through the singular application to Docker and ask for the open source exemption.

 

Does anyone from the LF have any visibility into where that work stands? (Trishan perhaps?)

 

Jim

 

From: tsc@... <tsc@...> On Behalf Of Dave Wallace
Sent: Wednesday, November 18, 2020 5:12 PM
To: infra-steering@...; tsc@...
Subject: [tsc] FD.io Nomad Infrastructure hitting Docker Hub Rate Limit

 

Folks,

FYI, today the FD.io Nomad CI has been starved of build executors due to hitting the Docker Hub Rate Limit [0] while using the 'fdiotools' account on docker hub.

I have opened an LF Help Desk Ticket [1] requesting that the 'fdiotools' account be upgraded either via Docker's Open Source Application process [2] or by upgrading the account to 'Pro' which costs $5 a month which will eliminate the issue ASAP.  Unfortunately until this is resolved there is likely to be daily outages of the FD.io CI pipeline.

Thanks,
-daw-

[0] https://www.docker.com/increase-rate-limits
[1] https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-21063
[2] https://www.docker.com/community/open-source/application