The only thing in container images I build are static binaries regardless of if it is C, rust, go, whatever. Static binaries don't defeat the point of containers, they are best practice. People that include bash and a package manager and such nonsense inside production containers huge complex and insecure for no reason.
The problem containers solve better than anything else are providing a simple API to take advantage of kernel security features that are a real pain to use otherwise.
User, process, and filesystem namespacing. System call filtering. Ensuring even if there is a remote exec exploit there is no bash or anything else in the container for an attacker to use.
If you think containers are only a software build and distribution tool then security is probably not even part of your thought process, and that is dangerous.
Ignore all the 99% of blog posts and tuturials on containers out there written by people who have never done any kind of system hardening.
They are mostly making your life harder and giving you nothing in return, as the author of this post points to.