elixir

Elixir is a dynamic, functional language for building scalable and maintainable applications.

GitHub repo: https://github.com/c0b/docker-elixir

Library reference

This content is imported from the official Docker Library docs, and is provided by the original uploader. You can view the Docker Hub page for this image at https://hub.docker.com/images/elixir

Supported tags and respective Dockerfile links

• 1.8.1, 1.8, latest (1.8/Dockerfile)
• 1.8.1-slim, 1.8-slim, slim (1.8/slim/Dockerfile)
• 1.8.1-alpine, 1.8-alpine, alpine (1.8/alpine/Dockerfile)
• 1.7.4, 1.7 (1.7/Dockerfile)
• 1.7.4-slim, 1.7-slim (1.7/slim/Dockerfile)
• 1.7.4-alpine, 1.7-alpine (1.7/alpine/Dockerfile)
• 1.6.6, 1.6 (1.6/Dockerfile)
• 1.6.6-slim, 1.6-slim (1.6/slim/Dockerfile)
• 1.6.6-alpine, 1.6-alpine (1.6/alpine/Dockerfile)
• 1.6.6-otp-21, 1.6-otp-21 (1.6/otp-21/Dockerfile)
• 1.6.6-otp-21-alpine, 1.6-otp-21-alpine (1.6/otp-21-alpine/Dockerfile)
• 1.5.3, 1.5 (1.5/Dockerfile)
• 1.5.3-slim, 1.5-slim (1.5/slim/Dockerfile)
• 1.5.3-alpine, 1.5-alpine (1.5/alpine/Dockerfile)
• 1.4.5, 1.4 (1.4/Dockerfile)
• 1.4.5-slim, 1.4-slim (1.4/slim/Dockerfile)

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-elixir/issues

• Maintained by:
  the Docker Community, with Elixir’s support

• Supported architectures: (more info)
  amd64, arm32v7, arm64v8, i386, ppc64le, s390x

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

• Image updates:
  official-images PRs with label library/elixir
  official-images repo’s library/elixir file (history)

• Source of this description:
  docs repo’s elixir/ directory (history)

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

What is Elixir?

Elixir is a dynamic, functional language designed for building scalable and maintainable applications.

Elixir leverages the Erlang VM, known for running low-latency, distributed and fault-tolerant systems, while also being successfully used in web development and the embedded software domain.

en.wikipedia.org/wiki/Elixir_(programming_language)

How to use this image

Run it as the REPL

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

Interactive Elixir (1.2.1) - press Ctrl+C to exit (type h() ENTER for help)
iex(1)> System.version
"1.2.1"
iex(2)>
➸ docker run -it --rm -h elixir.local elixir iex --sname snode
Erlang/OTP 18 [erts-7.2.1] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]

Interactive Elixir (1.2.1) - press Ctrl+C to exit (type h() ENTER for help)
iex(snode@elixir)1> System.version
"1.2.1"
iex(snode@elixir)2> :c.uptime
14 seconds
:ok

Run a single Elixir exs script

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

Image Variants

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

elixir:<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.

elixir:<version>-slim

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

elixir:<version>-alpine

This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.

This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn’t have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.

To minimize image size, it’s uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).

License

Copyright 2012 Plataformatec

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

View license information for the software contained in this image.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository’s elixir/ directory.

As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.