Re: Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

2020-10-28 Thread Roman Shaposhnik
On Wed, Oct 28, 2020 at 10:06 PM Chris Lambertus wrote: > > Hi Joan, > > I’m adding CC: vp-infra for visibility. > > The reason Infra aggressively prunes docker cache on the build nodes is that > projects generally do not clean up after their builds, and run the nodes out > of space with

Re: Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

2020-10-28 Thread Chris Lambertus
Hi Joan, I’m adding CC: vp-infra for visibility. The reason Infra aggressively prunes docker cache on the build nodes is that projects generally do not clean up after their builds, and run the nodes out of space with infinite docker images. Our donated general purpose build hardware resources

Re: Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

2020-10-28 Thread Dave Fisher
Hi Joan, I was vaguely concerned when I got that email. Thank you for sounding the alarm and presenting a reasonable choice of actions. The idea of an Apache Infra docker repos Is great! (Maybe dist.apache.org works?) A significant amount of time in Jenkins is spent building images which

Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

2020-10-28 Thread Joan Touzet
Got your attention? Here's what arrived in my inbox around 4 hours ago: > You are receiving this email because of a policy change to Docker products > and services you use. On Monday, November 2, 2020 at 9am Pacific Standard > Time, Docker will begin enforcing rate limits on container pulls