4 ms·
Again, this is recursion, if the upstream maintainer for the Apache and Nginx images is doing their job, the "yum update" should do nothing. Though, I agree, i
by fatherlinnux 11y ago
Again, this is recursion, if the upstream maintainer for the Apache and Nginx images is doing their job, the "yum update" should do nothing.
Though, I agree, it's very important to highlight that too much branching can cause massive environment bloat and way too many permutations.
If we just tell everyone to do yum updates at their layer this problem goes away. Ahh, recursion...
- gtrevorjay 11y agoThe issue is one of process/collaboration/composition. Even at the largest of distros, package maintainers usually act with pseudo independence. They can change, QA, and push their packages basically at will. Images are collections of those pushes. Even with automation the aggregate nature of images makes them qualitatively different and---especially organizationally---provides a process challenge.
- garethadams 11y agoWell, apart from "6) Don’t use only the “latest” tag". If I'm not using latest, and I don't know that the Apache and Nginx images have been updated, then it's very likely that "yum update" might do something.