Description of problem: Once source container are enabled, they will be included as regular types of the images in the repositories. Source container images are quite big, they cannot be pulled( podman docker pull will fail) and run. Only with skopeo copy command those containers can be installed. Satellite Registry won't have an issue to mirror down such content, however the sync time might be much longer due to the fact that source container images are quite large. This might decrease customer experience. Solution: add an option to opt out of mirroring source container images. Every source container will be tagged with the following convention: Source container images are named based on the binary containers they represent. For example, for a particular standard RHEL UBI 8 container registry.access.redhat.com/ubi8:8.1-397 append -source to get the source container image (registry.access.redhat.com/ubi8:8.1-397-source). We already have a whitelist option, adjust the code so it can handle regular expressions and a negation of the search pattern can be used. Version-Release number of selected component (if applicable): 6.7 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
This RFE is not on the roadmap in the short term, we will re-evaluate it in a few months.
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
reopening this as its a simple thing to do. We are simply going to prepopulate the exclude list with '*-source' upon new docker repo creation.
Created redmine issue https://projects.theforeman.org/issues/34398 from this bug
Verified in Satellite 6.11 Snap 18 Steps: 1. create a new product/repository 2. select docker from the content type dropdown 3. Observe the contents of the "Exclude tags" field Result: With the simpler solution mentioned in #6, we can see that *-source is the default value in the "Excluded Tags" field when creating a new docker repository. A user would have to consciously override this default to recreate the problem described in this bug. See attached screenshot
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5498