[sbarre]

I'm certainly not trying to argue or challenge anyone's interpretations of motive or assumptions of intent (no matter how silly I find them - we're all entitled to our opinions).

I am saying that when change is coming, particularly ambiguous or unclear change like many people feel this is, it's no one's responsibility but yours to make sure your production systems are not negatively affected by the change.

That can mean everything from confirming data with the platform vendor, to changing platforms if you can't get the assurances you need.

Y'all seem to be fixated on complaining about Docker's motives and behaviour, but none of that fixes a production system that's built on the assumption that these changes aren't happening.

[hansvm]

> but none of that fixes a production system that's built on the assumption that these changes aren't happening.

Somebody's going to have the same excuse when Google graveyards GCP. Till this change, was it obvious to anyone that you had to audit every PR fluff piece for major changes to the way Docker does business?

[sbarre]

> was it obvious to anyone that you had to audit every PR fluff piece for major changes to the way Docker does business?

You seem(?) to be assuming this PR piece, that first announced the change back in Sept 2024, is the only communication they put out until this latest one?

That's not an assumption I would make, but to each their own.

[flubbergusto]

Sure, but at least those of us reading this thread have learned this lesson and will be prepared. Right?

[hansvm]

Oh definitely.

This isn't exactly the same lesson, but I swore off Docker and friends ages ago, and I'm a bit allergic to all not-in-house dependencies for reasons like this. They always cost more than you think, so I like to think carefully before adopting them.