You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The alpine-slim images ship with a debug version of nginx at /usr/sbin/nginx-debug. This binary, intended just for debugging purposes, should not be included in the image since it increases the size unnecessarily, while the goal for slim images is to provide the bare minimum to have nginx working (and debugging it's not the bare minimum).
Shipping nginx-debug its like shipping an application to production with debugging symbols, which is definitely a bad practice.
Describe alternatives you've considered
I'm currently building my own version of this container and I remove that binary, but I believe this specifically is something that should come out of the box for everyone.
Additional context
If a user requires debugging for some special circumstance, a simple switch to the equivalent non slim tag would be enough.
The text was updated successfully, but these errors were encountered:
(slimmer is just rm -f /usr/sbin/nginx-debug). While I agree we're going to save some space by trimming it, having a slim image was never about the size - see discussions in #681 for instance.
Third, we use slim images as a base for non-slim ones, and removing the binary means we'd need to re-introduce package reinstall on those leaf images, which is a bit of an extra effort.
With that said, I don't think it's worth removing the binary just to save some space.
Describe the solution you'd like
The
alpine-slim
images ship with a debug version of nginx at/usr/sbin/nginx-debug
. This binary, intended just for debugging purposes, should not be included in the image since it increases the size unnecessarily, while the goal for slim images is to provide the bare minimum to have nginx working (and debugging it's not the bare minimum).Shipping
nginx-debug
its like shipping an application to production with debugging symbols, which is definitely a bad practice.Describe alternatives you've considered
I'm currently building my own version of this container and I remove that binary, but I believe this specifically is something that should come out of the box for everyone.
Additional context
If a user requires debugging for some special circumstance, a simple switch to the equivalent non
slim
tag would be enough.The text was updated successfully, but these errors were encountered: