DEPRECATED

The aarch64 organization is deprecated in favor of the more-specific arm64v8 organization, as per https://github.com/docker-library/official-images#architectures-other-than-amd64⁠. Please adjust your usages accordingly.

Supported tags and respective Dockerfile links

** THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289⁠ IS STILL IN-PROGRESS (which is the first step towards proper multiarch images) **

** PLEASE DO NOT USE THEM FOR IMPORTANT THINGS **

This image is built from the source of the official image of the same name (erlang). Please see that image's description for links to the relevant Dockerfiles.

If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the tianon/jenkins-groovy GitHub repository⁠, which are responsible for creating the Jenkins jobs which build them.

Quick reference

• Where to get help:
  the Docker Community Forums⁠, the Docker Community Slack⁠, or Stack Overflow⁠

• Where to file issues:
  https://github.com/c0b/docker-erlang-otp/issues⁠

• Maintained by:
  the Docker Community⁠

• Published image artifact details:
  repo-info repo's repos/erlang/ directory⁠ (history⁠)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/erlang⁠
  official-images repo's library/erlang file⁠ (history⁠)

• Source of this description:
  docs repo's erlang/ directory⁠ (history⁠)

• Supported Docker versions:
  the latest release⁠ (down to 1.6 on a best-effort basis)

What is Erlang?

Erlang is a programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of its uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance.

How to use this image

Run it as the REPL

➸ docker run -it --rm erlang
Erlang/OTP 18 [erts-7.1] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]

Eshell V7.1  (abort with ^G)
1> uptime().
3 seconds
ok
2>                                 % use Ctrl+G to call the shell switch
User switch command
 --> ?
  c [nn]            - connect to job
  i [nn]            - interrupt job
  k [nn]            - kill job
  j                 - list all jobs
  s [shell]         - start local shell
  r [node [shell]]  - start remote shell
  q                 - quit erlang
  ? | h             - this message
 --> q
➸ docker run -it --rm -h erlang.local erlang erl -name snode@erlang.local
Erlang/OTP 18 [erts-7.1] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]

Eshell V7.1  (abort with ^G)
(snode@erlang.local)1> erlang:system_info(otp_release).
"18"
(snode@erlang.local)2>
User switch command
--> q

Run a single Erlang escript

$ docker run -it --rm --name erlang-inst1 -v "$PWD":/usr/src/myapp -w /usr/src/myapp erlang escript your-escript.erl

Image Variants

The erlang images come in many flavors, each designed for a specific use case.

erlang:<version>

This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of buildpack-deps⁠. buildpack-deps is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system.

erlang:slim

This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run erlang. Unless you are working in an environment where only the erlang image will be deployed and you have space constraints, we highly recommend using the default image of this repository.

License

View license information⁠ for the software contained in this image.

1. From OTP 18 and above, Erlang is released under Apache License 2.0
2. The previous are released under Erlang Public License (EPL)⁠. EPL is a derivative work of the Mozilla Public License (MPL). It contains terms which differ from MPL, mainly in terms of jurisdiction. The license is constructed in accordance with the laws of Sweden.