Get the latest tech news
My personal reasons to not run my Nginx reverse-proxy inside Docker
Beware that this article is controversial to many people's opinions. It is no Docker-bashing prose! The following text is based on my situation why I consider wrapping my reverse-proxy (Nginx) with Docker as a disadvantage.
Ensures compatibility of the service (process) with the underlying OS Ensures compatibility of the service with the libraries and dependencies (avoids dependency hell) Prevents configuration drift (infrastructure is written as code) Eases spinning up more instances (e.g. for testing or scaling) Infrastructure-as-code serves as documentation The trivial case as an example: If something is unlikely to occur, easily detectable by the user (then also fixed) and has low severity then do not bother with the problem nor their solutions! If we run another instance of Nginx with the same configuration as in production - let's say for development - we need a full-blown DNS server to make it work.
Or read this on Hacker News