Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Damn, the Alphine linux ISO is tiny


Fedora 23 minimal image in docker: 43MB in archive.

With tons of packages available (with patches and live maintainers). With formal stabilization process. With well tested package management system (with hundreds of bug fixes in 20 years of use). Which can be used as host and as container (so you will need to learn well and support just one OS). With Systemd, which handles daemons well. With well supported LTS version (RHEL/CentOS). With option for paid support. With glibc, which is much faster and feature-richer than musl.

Why I should use Alpine, which cannot even handle versioned dependencies between packages? Literally, I cannot tell that package A needs package B >= 3.x or package C < 2.x, which causes serious troubles in complex systems.


Red Hat's Project Atomic "installer ISO" is ~630mb and the uncompressed qcow2 is >900mb.

I was impressed with Atomic's size, but seeing how much smaller Alpine is, I can't help but wonder what all the additional size is in Red Hat's images.


RHEL is an enterprise OS. It is designed to handle various drivers (video, network, storage). It has monitoring, auditing, reporting stuff. Some of those dependencies are bringing others (say the monitor needs a mail client to sent messages, ok, install the mail client, oh looks like that brings in perl, etc). Then there might be multiple version of said monitoring. And think they just never really try to make it small. That is just what their customers pay for.

If Alpine did what RHEL does out of the box it would be hundreds of MBs as well.


RHEL != Atomic


Atomic is intended to be used as a host OS and uses RHEL, CentOS, or Fedora as a base typically. And the installer ISO is that large precisely because it bundles hardware, language, and all kinds of other support.

However, if you'd like to craft your own minimal Atomic host, you can.

Making minimal containers is pretty easy, though, since yum/dnf lets you create execution trees that contain only what's needed for an application to run (as others have mentioned).

So, really, doing micro-services on RHEL/CentOS/Fedora hosts is pretty easy.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: