Thanks @ericmj, and hex team for building these. I just used one and it was so nice to not have to check what Alpine and ERTS version were being used. On top of that, the images are really small 
mmmries
4
jayjun
ericmj
Elixir Core Team
We have added images based on Ubuntu LTS versions. They are based on the following image tags:
ubuntu:bionic-20200219ubuntu:xenial-20200212ubuntu:trusty-20191217
Example tags:
hexpm/erlang:22.2.8-ubuntu-bionic-20200219hexpm/elixir:1.10.2-erlang-22.2.8-ubuntu-xenial-20200212
We also solved the issue of installing into the root of the filesystem in /erlang and /elixir by not using the precompiled builds and instead use make install to install in the correct locations according to the Filesystem Hierarchy Standard.
Next we are planning to add debian images. We also want to provide images for ARM architectures, but since we are no longer using the precompiled builds the option of cross-compiling is not possible. This means we either have to emulate ARM or use ARM hardware. I have tested the emulation option using docker buildx, but it seems far too slow, and we currently do not have access to ARM machines.
6
praveenperera
Thanks a lot for this! I love this approach.
It also makes it very easy for me to know which version of Alpine to pull from on my release container.
2
ericmj
Elixir Core Team
We have added builds based on debian and based on the ARM v8 architecture (called arm64 on Docker). The new debian images are based on the following image tags:
debian:buster-20200224debian:stretch-20200224debian:jessie-20200224
We use “fat manifests” to be able to serve both amd64 and arm64 using the same image tag names, that means you can docker pull hexpm/erlang:22.3-alpine-3.11.3 and docker will figure out the correct architecture to pull for your system. We provide arm64 images for all the same versions we provide amd64 images as long as we are able to build Erlang and Elixir on the given versions, but some older distributions and Erlang versions do not fully support ARM.
6