The rise of containerization has brought about a double-edged sword in terms of security and administration. On one hand, containers offer the convenience of isolating applications from system libraries and dependencies, making it easier to update and patch them without affecting the underlying system. However, this convenience comes with a significant cost - increased complexity, slower update cycles, and potential security risks. As someone who's seen firsthand the issues caused by containerization, I've come to dread the thought of having to keep multiple versions of shared libraries active in my systems. The proliferation of shadow package managers like npm and pip has only made things worse, with their complex dependency trees and rarely updated versions leading to a treasure trove of security vulnerabilities. In this article, I'll explore the dark side of containerization and why, as a seasoned administrator, I've chosen to avoid these containers at all costs. Join me as we delve into the world of Docker, Snap, Flatpack, and other package managers, and discover why they're not the silver bullet to security and administration that they claim to be.