logoalt Hacker News

_blk01/21/20252 repliesview on HN

My kind of nerd humor but I read the article only to find that the question I had going into it is not answered: How large might those containers (with/without community) get?

Who's taking the nerd-snipe bait? ;)


Replies

chamlis01/21/2025

Author here. I did run these numbers, I guess I just didn't think to write them up. I've recomputed them for Alpine 3.21 here.

Maximising the number of packages gives 5492/5536 packages (99.2%) for just main, with a total install size of 17.03GiB. Including community gives 25026/25383 packages (98.6%) with a total install size of 107.85GiB.

If we instead maximise the total installed size directly, we install 5428/5536 (98.0%) packages from main, with a total install size of 17.06GiB. Including community gives 24711/25383 packages (97.4%) with a total install size of 110.36GiB.

Of course, if you're building a container, it would be redundant to install a kernel, so these numbers are somewhat inflated.

show 2 replies
diggan01/21/2025

> How large might those containers (with/without community) get?

Thrown together awk summing alpine main repository as of v3.21:

    awk -F ':' '/^I:/ { sum += $2 } END { print sum }' APKINDEX | numfmt --to=iec --suffix=B
Returns 18GB. Author landed on 98.5% of packages being installable together, ~17.7GB in total, once installed. Community ends up being 100GB with 97.8%, so 97.8GB and final size ends up being ~115GB.

Probably not even the largest image out there, but large enough to be too large :)

show 1 reply