Bob performs automated tasks for the Elixir and Hex projects.
Erlang builds compiled on Ubuntu LTS versions are built periodically. Bob checks for new tagged releases every 15 minutes and builds any new versions it discovers. The "master" and "maint*" branches are built once a day.
After the builds complete they will be available at https://builds.hex.pm/builds/otp/${ARCH}/${OS_VER}/${REF}.tar.gz where ${ARCH} is the CPU architecture, ${OS_VER} is the OS name and version, and ${REF} is the name of the git tag or branch.
Supported architectures:
amd64arm64
Supported OS versions:
ubuntu-22.04ubuntu-24.04ubuntu-26.04
Examples of URLs are:
- https://builds.hex.pm/builds/otp/arm64/ubuntu-22.04/OTP-26.0.tar.gz
- https://builds.hex.pm/builds/otp/amd64/ubuntu-24.04/maint.tar.gz
For lists of builds see:
amd64:arm64:
Docker images for Bob's Elixir and Erlang builds are built periodically. Bob checks for new Elixir and Erlang releases every 15 minutes and builds images for any new versions it discovers. The list of operating system distributions we base the images on is defined by builds/0 in https://github.com/hexpm/bob/blob/main/lib/bob/job/docker_checker.ex.
Bob automatically builds the latest patch release of every version family: the newest release per Erlang major.minor line (for example only 26.2.5.21 out of the 26.2.x line) and the newest Elixir patch release per minor version, for every compatible OTP major. Older patch versions are not built automatically but can be requested manually, see below.
Tagged images are never changed, that means hexpm/erlang@22.0-alpine-3.11.2 will always target the tag OTP-22.0 and won't update when OTP-22.0.1 is released.
Erlang builds are found at https://hub.docker.com/r/hexpm/erlang, they use the versioning scheme ${OTP_VER}-${OS_NAME}-${OS_VER} for tags.
Elixir builds are found at https://hub.docker.com/r/hexpm/elixir, they use the versioning scheme ${ELIXIR_VER}-erlang-${OTP_VER}-${OS_NAME}-${OS_VER}.
Builds are provided for the following OS and architectures using the docker OS/ARCH scheme:
linux/amd64linux/arm64/v8
All provided images and tags can be searched at https://bob.hex.pm/docker.
hexpm/erlang:22.2.8-alpine-3.11.3hexpm/erlang:22.2-ubuntu-bionic-20200219hexpm/elixir:1.10.2-erlang-22.2.8-alpine-3.11.3hexpm/elixir:1.10.0-erlang-22.2-ubuntu-bionic-20200219
If you need a specific patch version that is not built automatically, request it at https://bob.hex.pm/request. Sign in with your hex.pm account, then pick the image kind (Erlang or Elixir), the OS and base image version, and the exact Erlang (and Elixir) version. The image is built for both architectures, including the multi-arch manifest; when an Elixir image needs an Erlang base image that does not exist yet, the base is built first and the Elixir image follows automatically.
Requested builds are limited to ten image builds per user per hour. Build progress can be followed on the jobs dashboard at https://bob.hex.pm.
Requesting an image also reserves it from cleanup, permanently. If the image already exists it is reserved without rebuilding. The multi-arch images you pull are never removed anyway, so this only matters for the per-architecture build images (see Retention and cleanup below).
The images you pull are never removed. Every tag in hexpm/erlang and hexpm/elixir stays available indefinitely, however old it is and however rarely it is used.
Cleanup only touches hexpm/elixir-amd64 and hexpm/elixir-arm64, which hold the single-arch images the multi-arch manifests are assembled from rather than images meant to be pulled directly. They keep the last 30 days of builds; older single-arch tags are removed, and the multi-arch image they back stays available.
Tags reserved by a build request are never removed and are flagged as reserved. To pin a single-arch tag indefinitely, request it at https://bob.hex.pm/request.