containmint 0.4.0

Why another tool?

Most existing tools and services rely on QEMU to perform container builds on other architectures. These builds are much slower, often running 15x longer than native builds.

Additionally, using customizable virtual machines allows for builds which dedicated build services may not support.

How does it work?

Ephemeral virtual machines are provisioned through the Ansible Core CI service [1]. These virtual machines are used to perform native container builds. The resulting images are pushed to a container registry.

After the container images are pushed, a manifest list referencing the container images is created. The manifest list is then pushed to a container registry.

Footnotes

Configure container registry credentials

The credentials [2] for the container registry [3] are set using environment variables:

export CONTAINMINT_USERNAME = 'my-username'
export CONTAINMINT_PASSWORD = 'my-password'

Footnotes

Build and push a multi-arch container

The following steps can be performed in parallel:

containmint build --push --tag quay.io/my_org/scratch_repo:my_tag-x86_64 --arch x86_64
containmint build --push --tag quay.io/my_org/scratch_repo:my_tag-aarch64 --arch aarch64

Once the steps above have been completed:

containmint merge --push \
  --tag quay.io/my_org/final_repo:my_tag \
        quay.io/my_org/scratch_repo:my_tag-x86_64 \
        quay.io/my_org/scratch_repo:my_tag-aarch64

This results in three tags:

• quay.io/my_org/final_repo:my_tag – This manifest list contains x86_64 and aarch64 images.

• quay.io/my_org/scratch_repo:my_tag-x86_64 – This image is x86_64 only.

• quay.io/my_org/scratch_repo:my_tag-aarch64 – This image is aarch64 only.