2 ms·
> This broke production environments. This broke development environments. I really hope no one is using Docker Desktop running on Mac in production. Not to
by kelnos 6y ago
> This broke production environments.
This broke development environments. I really hope no one is using Docker Desktop running on Mac in production.
Not to trivialize the issue; lost productivity due to a a bug in a software update sucks. But people are not getting irate customer phone calls or losing revenue because of product downtime due to this.
- asidiali 6y agoGood point, thank you for the correction.
- k_sze 6y ago> But people are not getting irate customer phone calls or losing revenue because of product downtime due to this. It could be an indirect cause of irate calls because there’s a bug in production but the dev environment is broken by Docker’s auto-update so the devs can’t work on a fix for the production bug.
- jackinloadup 6y agoDude! This exactly. Think about having to explain that to NASA. Ahh sorry I can't fix this major SEC issue because our developers can't do a release atm. It went over as well as you'd think. I had to pull out our actual contract to be like "Well... we actually have like 8 days to fix this criticality of SEC so..." Then prayed to Al Gore and Linus Torvalds that what ever this dependency was would be resolved before I got my ass handed to me.
- dragonwriter 6y ago> This broke development environments. I really hope no one is using Docker Desktop running on Mac in production. If it breaks even just my desktop working environment, and that impairs my ability to remediate a production problem, it's causing production downtime. Dev environments aren't decorative.