3 ms·

Interesting read. I'd like to know more about alpine problems (even just to confirm my bias against it, unless space savings are the most important thing). For

Interesting read. I'd like to know more about alpine problems (even just to confirm my bias against it, unless space savings are the most important thing). For me, Hetzner is mostly baremetal provider. They have dedicated RX line, and if you have base load, a couple of those could run it all (use hetzner cloud instances for scalling and failover)

novakwok 3y ago
[I'd like to know more about alpine problems] Sure, and we're planning to share another post later on the whole procedure of our migration from AMD64 to ARM64, and in that post we'll include more details about Clickhouse's problem if we can definitively establish that the problem was caused by alpine. (After this incident I personally have bias against alpine images too Comparing alpine and non-alpine images on DockerHub: https://hub.docker.com/layers/clickhouse/clickhouse-server/23.4-alpine/images/sha256-8160aa2ad15b7c922c08fc2ff826c5e0702a54150337791e57c9f738d90d5d43?context=explore https://hub.docker.com/layers/clickhouse/clickhouse-server/2... https://hub.docker.com/layers/clickhouse/clickhouse-server/23.4/images/sha256-343b921e14c91baef6592e266e2c47941f2e3d6f23ee62f5997ae39f93688bb9?context=explore https://hub.docker.com/layers/clickhouse/clickhouse-server/2... There is just ~66MB(255MB vs 321MB) of size difference, my personal advice after this to to avoid alpine images in production as much as possible :P