---
title: "Comment by OneLifeVibe on \"NGINX2Root: What Five Memory Bugs in Your Web Server Teach About Patching\" | Hashnode"
description: "The point about NGINX hiding inside ingress controllers and containers stood out. It is easy to patch the main web server and miss the copies bundled elsewhere."
url: "https://hashnode.com/posts/nginx2root-what-five-memory-bugs-in-your-web-server-teach-about-patching/6aff3244f4be884b35df7453/comment/6aff5a22bd5e4bccd338da14"
---

[Discussion](https://hashnode.com/posts/nginx2root-what-five-memory-bugs-in-your-web-server-teach-about-patching/6aff3244f4be884b35df7453)

Comment [NGINX2Root: What Five Memory Bugs in Your Web Server Teach About Patching](https://hashnode.com/posts/nginx2root-what-five-memory-bugs-in-your-web-server-teach-about-patching/6aff3244f4be884b35df7453)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[11h ago](https://hashnode.com/posts/nginx2root-what-five-memory-bugs-in-your-web-server-teach-about-patching/6aff3244f4be884b35df7453/comment/6aff5a22bd5e4bccd338da14)

The point about NGINX hiding inside ingress controllers and containers stood out. It is easy to patch the main web server and miss the copies bundled elsewhere. The nginx -T inventory step feels like the right starting point, since you cannot patch what you have not found. The reminder to fully restart after upgrading also matters, because an upgrade that never takes effect leaves the same risk in place.
