Skip to content

Comment on We reduced a container image from 800GB to 2GBparent

Comments

I can't think of anything that would justify that many layers. If I have that much complexity, I would split up the container or start writing bash scripts.

The automation of containers looks simple but developers with systems experience know the actual complexity of operating systems and running applications.

People who know javascript but don't know how a file system works can build and deploy containers. They just copy and paste stuff until it runs. The automation of containers makes brute force iteration a viable option. It was a lot more difficult trying to run a Linux server, which would force you to learn something or use a platform as a service instead.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.