Sunday, 2024-12-22

*** dhill is now known as Guest376101:06
*** \join_su1line is now known as \join_subline22:27
tonybHow do I verify/ensure that any/all jobs in a given build are pulling container images through the mirror/buildset registry?22:48
tonybI keep hitting the docker.io ratelimits22:48
Clark[m]tonyb: we disabled the mirror by default because that funneled everything through one IP which seemed to increase the rate of rate limit problems 23:10
Clark[m]Then the buildset registry is typically only used for images built in the same buildset..however things could be modified to prime the buildset registry with all needed images 23:10
tonybClark[m]: Ahh that makes sense23:12
Clark[m]Unfortunately an entire /64 is treated as one IP for ipv623:17
Clark[m]So even with disabling the mirror we're kinda funneling on some clouds23:17
Clark[m]We could modify jobs with ipv4 records for the two docker hub names23:18
Clark[m]In /etc/hosts I mean23:19
tonybYeah.  I'll look into something like that23:19
Clark[m]Review02 has the two names commented out in /etc/hosts23:20
Clark[m]Ideally we lookup the values at runtime though as they may do global DNS load balancing23:21
tonybYeah.  I have a couple of ideas23:25
tonyb`for host in docker.io registry-1.docker.io production.cloudflare.docker.com ; do host -t A $host | awk "{print \$NF, \"$host\"}"; done | tee -a  /etc/hosts`23:26
tonybmight work?23:26
Clark[m]The shape of that looks right. I'm a passenger in a car so can't really test or debug it23:51

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!