It can be, yes. One of the largest complaints with Docker is that you often end up running the same dependencies a dozen times, because each of your dozen containers uses them. But the trade-off is that you can run a dozen different versions of those dependencies, because each image shipped with the specific version they needed.
Of course, the big issue with running a dozen different versions of dependencies is that it makes security a nightmare. You’re not just tracking exploits for the most recent version of what you have installed. Many images end up shipping with out-of-date dependencies, which can absolutely be a security risk under certain circumstances. In most cases the risk is mitigated by the fact that the services are isolated and don’t really interact with the rest of the computer. But it’s at least something to keep in mind.
I occasionally do scale drawings for my job, and I occasionally have to remind my coworker that her nice pretty colorized drawings will look fucking atrocious when printed in greyscale on a shitty laser printer. She likes to color code things to make it easier to communicate info… But that often ends up making things harder on the crews who are actually executing things. Because when she used color to communicate something, but the entire drawing is printed in shades of grey to hand a hard copy to the crew, it becomes fucking impossible to actually follow the drawing.
For instance… The yellow circle is the one we need done today. Here’s what she draws:
Except here’s what the crew receives:
Now imagine if this was a watermark on every page of a 50 page court filing, which then gets printed out for the judge. Now they’re seeing text on the grey background, which likely makes it harder to read and is a massive waste of toner. It also massively inflates pdf file sizes, because you’re sending that image on every single page.