News for hackers. Stuff that matters.
Re:Docker Systems Status: Full Service Disruption by cebert on Monday October 20, 2025 @05:12AM (#45641683)
I’m not sure that the impact will be that big. Most organizations have their own mirrors for artifacts.
Re:Docker Systems Status: Full Service Disruption by VenturingVole on Monday October 20, 2025 @05:14AM (#45641699)
From what I've seen: I highly doubt it.

Edit to add: This might spur on a few more to start doing that, but people are quick to forget/prioritise other areas. If this keeps happening then it will change.

Re:Docker Systems Status: Full Service Disruption by nusl on Monday October 20, 2025 @05:19AM (#45641743)
Yeah, perhaps. I don't know how many folks host mirrors. Most places I've worked for didn't, though this is anecdotal.
Re:Docker Systems Status: Full Service Disruption by phillebaba on Monday October 20, 2025 @05:41AM (#45641922)
I would say most people would say it't best practice while a minority actually does it.
Re:Docker Systems Status: Full Service Disruption by CaptainOfCoit on Monday October 20, 2025 @06:14AM (#45642188)
Seems related to size and/or maturity if anything. I haven't seen any startups less than five year old doing anything like that, but I also haven't seen any huge enterprise not doing that, YMMV.
Re:Docker Systems Status: Full Service Disruption by walkabout on Monday October 20, 2025 @12:02PM (#45645449)
“Their own” can and often does mean something hosted on a major cloud provider (whether they manage it in-house or pay a vendor for their system)