Releases: containerbuildsystem/atomic-reactor
Releases · containerbuildsystem/atomic-reactor
1.6.40
Requires osbs-client >= 0.48
and dockerfile-parse >= 0.0.11
Build JSON API changes
arrangement_version
<= 5 support has been removed (in version 1.6.40)
Bug Fixes
None
Improvements
- Verify parent images digests stored in koji builds against the digests of the manifests stored in the internal registry. Whenever they differ, the build will fail.
- Do not allow builds to use images that were not built with OSBS (not in koji).
- Add skip_koji_check_for_base_image config option to allow non-OSBS built images to be used as parent images
- Dropped support for container registry API V1
- Dropped support for V1 content
- Operator builds now use their own
operator-manifests
koji build type to upload artifacts to. This means that such archives can no longer be fetched from the build logs. - Catch all exceptions for get_archive and remove_container
1.6.39.1
Requires osbs-client >= 0.48
and dockerfile-parse >= 0.0.11
Build JSON API changes
arrangement_version
<= 5 support will be removed in version 1.6.40
Bug Fixes
- don't fail build if primary tag exists in registry
Improvements
None
Deprecation warning
- Support for container registry API V1 will be dropped in future releases
1.6.39
Requires osbs-client >= 0.48
and dockerfile-parse >= 0.0.11
Build JSON API changes
arrangement_version
<= 5 support will be removed in version 1.6.40
Bug Fixes
- python 2/3 compatibility fixes
- Handle exceptions when using docker-py v3.x
Improvements
- Add support for 'modular_koji_tags' in ODCS compose builds
- Verify media types plugin returns list of found types or
manifest list type - Retry docker operations if a ReadTimeoutError is raised
- Fail build when vr tag for image already exists
- Fail build when explicit release is set in Dockerfile and koji build already exists (for non-scratch builds)
- Don't overwrite com.redhat.license_terms label with default value
- Added support for quay.io private repositories for source image pulls. Some quay.io organizations do not support v2 schema and may generate
Missing platforms for registry quay.io
errors. - Better internal separation of floating tags and primary tags
- Doubled ODCS timeout, now 3600s
Deprecation warning
- Support for container registry API V1 will be dropped in future releases
1.6.38.1
1.6.38
Requires osbs-client >= 0.48
and dockerfile-parse >= 0.0.11
Build JSON API changes
arrangement_version
<= 5 is deprecated and support will be removed in version 1.6.39
Bug Fixes
- Request architectures on module compose requests
- only include manifest digests in archive metadata if they can be fetched by digest
- allow atomic-reactor-repo directory in .dockerignore file, when it exists
Improvements
- Removed obsolete add_yum_repo plugin
- Propagate logging level to osbs-client
- Check if parent image koji build has not been removed
- Improve error message when fetching a worker metadata fails by reporting the failing platform name
- Forward Go package information in container.yaml to koji (towards container first builds)
- Retry push when v2 s2 or oci is missing and required
- composes can contain packages, modules, and pulp components instead of being limited to pulp and either packages or modules components
- inherit yum repos and composes from baseimage
- get the git commit depth from osbs-client and use that value to perform shallow clones of git repositories, dramatically decreasing the load on git servers.
- add new extract_operator_manifests plugin. It is now possible to set a
com.redhat.delivery.appregistry
label to "true" in Dockerfile to allow files under/manifests
in the built image to be uploaded to koji in aoperator_manifests.zip
archive
1.6.37.1
1.6.37
Requires osbs-client >= 0.48
and dockerfile-parse >= 0.0.11
Build JSON API changes
arrangement_version
<= 5 is deprecated and support will be removed in version 1.6.38
Bug Fixes
- Custom base images now properly work with multistage
- Custom base images work with organization defined
- Request registry push access when grouping manifests
Improvements
- Allow dckercfg 'auth' to be used for authentication (instead of username and password)
- Check requested plugins availability before build process (aborts if required plugin is missing)
- Do not reload plugins before each phase. Instead, load all plugins before entering build
- Allow FROM scratch base image
- Improve logging for platforms in limits
- module composes can specify an empty packages key, and the compose will include all packages associated with the base image's koji tag.
- orchestrator collects images digests which are used by workers to prevent a race condtition when tags may change during worker builds.
- when release label isn't specified for scratch builds, openshift build id will be used as value
- specify time units in pulp repository operation log messages
- each plugin decides for itself whether to run for a custom base images, instead of some plugins being disabled by osbs-client
- upload metadata for scratch builds
1.6.36.1
1.6.36
Requires osbs-client >= 0.48
and dockerfile-parse >= 0.0.11
Build JSON API changes
arrangement_version
<= 5 is deprecated and support will be removed in version 1.6.38
Bug Fixes
- ensures that '.repo' is always at the end of a yum repo URL
- empty sections allowed in
container.yaml
post_group_manifests
runs properly without grouping manifests on non-amd64 platform- ODCS: Start the compose with the correct architectures
flatpak_base_image
has been removed from user params schema (Part of: flatpak base image is now properly loaded from a reactor-config-map)- Flatpak: pass compose ids to the worker builds correctly
Improvements
- Ability to request ODCS composes with multilib
registries_organization
now used for source registry- koji target build parameter is used as default value for createImage tasks
- Component mismatches are reported more clearly
- Clearer error when yum repo URL cannot be fetched
import_image
plugin uses now import_image_tags, which imports image and tags at once, instead of importing tags one by one, and import image after- Signal handler added for SIGUSR1 to aid in debugging
image-build.conf
default name and version are taken from Dockerfile labels (if defined)- LABEL
com.redhat.component
is used as default value forname
- LABEL
version
is used as default value forversion
- LABEL
- koji builds now display the koji name-nvr and digests with versions in the metadata under extra.osbs.koji
- error reporting of a missing image in registries is more user friendly now
- fixed error reporting: exit plugins don't hide the original root cause by raising different exception
- possibility to specify 'name' and 'component' for flatpaks to override labels in generated Dockerfile
1.6.35.1
Requires osbs-client >= 0.48
and dockerfile-parse >= 0.0.11
Build JSON API changes
None
Bug Fixes
get_koji_module_build
handles change to the "archives" that MBS writesflatpak_create_dockerfile
Initialize /etc/os-release in the installrootget_koji_module_build
handles streams with dashes
Improvements
- Support for ODCS signing intents added for Flatpaks
- WrappedDocker: Work around export inefficiency in older docker-python