almalinux/pungi
15
2
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
2,961 Commits 3 Branches 369 Tags 8.3 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
ac7e1e515e
Go to file
Adam Williamson ac7e1e515e Use new container and bootable-container productmd types 
In https://github.com/release-engineering/productmd/pull/181 I
added new `bootable-container` and `container` types to
productmd. This makes pungi always use the bootable-container
type for ostree_container images (previously 'ociarchive'), and
default to using the container type for Kiwi-built oci.tar.xz
container images (previously 'docker').

This is a significant change for anything that relies on
productmd/fedfind conventions to 'identify' images, as these
images will now have a different identity. But I think it's a
valuable improvement in their identities. 'ociarchive' never made
any sense as an image 'type' - it's a format - and 'docker'
wasn't a very good type for images that are explicitly OCI
container images, not Docker-native ones. We also can now easily
distinguish between 'regular' container images and ones that are
intended to be bootable.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
(cherry picked from commit 3cb8992d56f2cee8a7cb151253125e30931ccd6d)
2025-09-29 18:26:35 +03:00
contrib Add config file for cleaning up cache files 2023-11-10 16:51:51 +02:00
doc Release 4.8.0 2025-09-29 18:23:51 +03:00
pungi Use new container and bootable-container productmd types 2025-09-29 18:26:35 +03:00
pungi_utils Drop usage of six 2025-09-29 18:23:44 +03:00
share Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag. 2018-03-21 14:33:45 +01:00
tests Directly import mock from unittest 2025-09-29 18:26:35 +03:00
.gitignore nomacboot option for livemedia koji tasks 2022-03-23 09:36:51 +01:00
1860.patch Release 4.10.1 2025-09-29 18:14:47 +03:00
AUTHORS extra-files: Write a metadata file enumerating extra files 2016-09-07 13:02:48 +02:00
COPYING Remove FSF address from comments 2016-09-23 10:26:43 +02:00
git-changelog git-changelog: Fix running on Python 3 2019-07-02 15:05:25 +02:00
GPL Update GPL to latest version from https://www.gnu.org/licenses/gpl-2.0.txt 2015-06-25 07:50:03 -04:00
Makefile Use pytest instead of nosetests 2020-07-29 14:57:16 +08:00
MANIFEST.in Default bztar format for sdist command 2023-11-10 16:50:33 +02:00
pungi.spec Release 4.10.1 2025-09-29 18:14:47 +03:00
README.md Correct irc network name & add matrix room 2021-10-25 07:26:18 +00:00
requirements.txt Remove python 2.7 from tox configuration 2025-09-29 18:23:45 +03:00
setup.cfg Default bztar format for sdist command 2023-11-10 16:50:33 +02:00
setup.py Use new container and bootable-container productmd types 2025-09-29 18:26:35 +03:00
sources Release 4.10.1 2025-09-29 18:14:47 +03:00
test-requirements.txt Remove python 2.7 from tox configuration 2025-09-29 18:23:45 +03:00
TODO Drop buildinstall method 2024-08-30 13:30:35 +03:00
tox.ini Remove python 2.7 from tox configuration 2025-09-29 18:23:45 +03:00

README.md

Pungi

Pungi is a distribution compose tool.

Composes are release snapshots that contain release deliverables such as:

  • installation trees
    • RPMs
    • repodata
    • comps
  • (bootable) ISOs
  • kickstart trees
    • anaconda images
    • images for PXE boot

Tool overview

Pungi consists of multiple separate executables backed by a common library.

The main entry-point is the pungi-koji script. It loads the compose configuration and kicks off the process. Composing itself is done in phases. Each phase is responsible for generating some artifacts on disk and updating the compose object that is threaded through all the phases.

Pungi itself does not actually do that much. Most of the actual work is delegated to separate executables. Pungi just makes sure that all the commands are invoked in the appropriate order and with correct arguments. It also moves the artifacts to correct locations.

Links