Metadata-Version: 2.1
Name: containmint
Version: 0.2.0
Summary: Create multi-arch containers using native cloud builds.
Author-email: Matt Clay <matt@mystile.com>
Maintainer-email: Matt Clay <matt@mystile.com>, Matt Davis <mrd@redhat.com>
Requires-Python: >=3.9,<3.11
Description-Content-Type: text/x-rst
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: GNU General Public License v3 or later (GPLv3+)
Classifier: Natural Language :: English
Classifier: Operating System :: POSIX
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.9
Classifier: Topic :: Software Development :: Build Tools
Classifier: Topic :: Utilities
Requires-Dist: ansible-core == 2.13.1
Requires-Dist: argcomplete ; extra == "argcomplete"
Project-URL: Bug Tracker, https://github.com/ansible/containmint/issues
Project-URL: CI: Azure Pipelines, https://dev.azure.com/ansible/containmint/
Project-URL: Changelog, https://github.com/ansible/containmint/blob/main/CHANGELOG.rst
Project-URL: Documentation, https://github.com/ansible/containmint/blob/main/README.rst
Project-URL: Homepage, https://github.com/ansible/containmint
Project-URL: Source Code, https://github.com/ansible/containmint
Provides-Extra: argcomplete

containmint
===========

Create multi-arch containers using native cloud builds.

Q&A
===

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 [#ansible_core_ci]_.
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.

.. rubric:: Footnotes

.. [#ansible_core_ci] Authentication is required.
   An API key must be provided, or the tool must be run from an approved organization at a supported CI provider.

Usage Examples
==============

Configure container registry credentials
----------------------------------------

The credentials [#no_login]_ for the container registry [#one_registry]_ are set using environment variables:

.. code-block::

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

.. rubric:: Footnotes

.. [#no_login] Use the ``--no-login`` option to allow operation without credentials.
   This option is only usable when not pushing to a container registry.

.. [#one_registry] Only one container registry can be used with each invocation.
   Multiple repositories from the same registry can be used.

Build and push a multi-arch container
-------------------------------------

The following steps can be performed in parallel:

.. code-block::

   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:

.. code-block::

   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.

