News for hackers. Stuff that matters.

A comment on Docker Apology. Parent comment

Re:Docker Apology by francislavoie on Friday March 17, 2023 @03:02AM (#35194124)
You missed his point. He's saying "latest is an anti-pattern". Which is correct. Everyone should be pinning to specific versions or semver to avoid being accidentally upgraded to a release with breaking changes.

Yes, obviously making existing tags immutable is bad. Nobody is disputing that.

[ Parent | on HN ]
Re:Docker Apology by code_biologist on Friday March 17, 2023 @03:15AM (#35194209)
There are exceptions though. I'm the kind of person that would pin Jenkins to latest even if it is an antipattern. I'm way more concerned about security flaws than a temporary CI breakage. So for me: Everyone should be pinning Jenkins to latest to avoid accidentally staying on a release with security holes.
[ Parent | on HN ]
Re:Docker Apology by rightbyte on Friday March 17, 2023 @05:49AM (#35195027)
You are not only auto pulling fixes bit also auto pulling new security holes though.

My take on Jenkins with all its plugins is that it need to be properly shielded from external access anyways.

[ Parent | on HN ]
Re:Docker Apology by 3np on Friday March 17, 2023 @08:25AM (#35196146)
You probably want to pin to at least a major tag to avoid auto-pulling breaking changes at any moment but still getting security updates.
[ Parent | on HN ]