cimg/elixir pulls statistics

CircleCI Convenience Images => Elixir

A Continous Integration focused Elixir Docker image built to run on CircleCI

*This image is designed to supercede the legacy CircleCI Elixir image, circleci/elixir.*

cimg/elixir is a Docker image created by CircleCI with continuous integration builds in mind. Each tag contains a complete Elixir installation for use with mix and hex.

Table of Contents

• Getting Started • How This Image Works • Development • Contributing • Additional Resources • License

Getting Started

This image can be used with the CircleCI docker executor. For example:

In the above example, the CircleCI Elixir Docker image is used as the primary container. More specifically, the tag 1.9 is used meaning the version of elixir will be v1.9. You can now use mix within the steps for this job.

How This Image Works

This image contains both Elixir as well as a supported version of Erlang.

Parent Tags and Parent Slugs

Parent Tags introduce the ability to choose a specific version to include in the tag. In conjunction with the Parent Slug, Elixir now supports choosing which Erlang version to use and looks like: parentSlug-parentTag, which would translate to erlang-22.3

Variants

Variant images typically contain the same base software, but with a few additional modifications.

Node.js

The Node.js variant is the same Elixir image but with Node.js also installed. The Node.js variant can be used by appending -node to the end of an existing cimg/elixir tag.

Browsers

The browsers variant is the same Elixir image but with Node.js, Selenium, and browser dependencies pre-installed via apt. The browsers variant can be used by appending -browsers to the end of an existing cimg/elixir tag. The browsers variant is designed to work in conjunction with the CircleCI Browser Tools orb. You can use the orb to install a version of Google Chrome and/or Firefox into your build. The image contains all of the supporting tools needed to use both the browser and its driver.

Tagging Scheme

This image has the following tagging scheme:

- The version of Elixir to use. This can be a full SemVer point release (such as 1.10.2) or just the minor release (such as 1.10). If you use the minor release tag, it will automatically point to future patch updates as they are released by the Elixir project. For example, the tag 1.10 points to elixir 1.10.2 now, but when the next release comes out, it will point to 1.10.3.

- This specifies the erlang version to use in accordance with the compatibility chart. Note: the default image tag: cimg/elixir:[-variant] will utilize the latest version e.g 24.3

[-variant] - Variant tags, if available, can optionally be used. For example, the Node.js variant can be used like this: cimg/elixir:1.10.1-node.

Development

Images can be built and run locally with this repository. This has the following requirements:

• local machine of Linux (Ubuntu tested) or macOS • modern version of Bash (v4+) • modern version of Docker Engine (v19.03+)

Cloning For Community Users (no write access to this repository)

Fork this repository on GitHub. When you get your clone URL, you'll want to add --recurse-submodules to the clone command in order to populate the Git submodule contained in this repo. It would look something like this:

If you missed this step and already cloned, you can just run git submodule update --recursive to populate the submodule. Then you can optionally add this repo as an upstream to your own:

Cloning For Maintainers ( you have write access to this repository)

Clone the project with the following command so that you populate the submodule:

Generating Dockerfiles

Dockerfiles can be generated for a specific elixir version using the gen-dockerfiles.sh script. For example, to generate the Dockerfile for elixir v1.10.2, you would run the following from the root of the repo:

The generated Dockerfile will be located at ./1.10//Dockefile in addition to their corresponding variants located at ./1.10///Dockefile

To build this image locally and try it out, you can run the following (assuming a 23.3 erlang version):

If using the default version (latest), you could run either of the following:

Building the Dockerfiles

To build the Docker images locally as this repository does, you'll want to run the build-images.sh script:

This would need to be run after generating the Dockerfiles first. When releasing proper images for CircleCI, this script is run from a CircleCI pipeline and not locally.

Submitting a Pull Request

Ensure all the changes to the versioned Dockerfiles and the build-images.sh have been reverted, leaving only the Dockerfile.template as the modified file. These will have been modified while testing with the sections above. The specific versions will be included when the images are released.

Publishing Official Images (for Maintainers only)

The individual scripts (above) can be used to create the correct files for an image, and then added to a new git branch, committed, etc. A release script is included to make this process easier. To make a proper release for this image, let's use the fake elixir version of v99.9.9, you would run the following from the repo root:

This will automatically create a new Git branch, generate the Dockerfile(s), stage the changes, commit them, and push them to GitHub. The commit message will end with the string [release]. This string is used by CircleCI to know when to push images to Docker Hub. All that would need to be done after that is:

• wait for build to pass on CircleCI • review the PR • merge the PR

The master branch build will then publish a release.

Incorporating Changes

How changes are incorporated into this image depends on where they come from.

build scripts - Changes within the ./shared submodule happen in its own repository. For those changes to affect this image, the submodule needs to be updated. Typically like this:…

Description from the Docker Hub listing.