Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Our UBI yum repositories include the sudo package, however this is not included by default in the base images themselves. Azure currently runs everything via sudo and therefore our base images do not work in that environment.
Version-Release number of selected component (if applicable):
ubi8
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
https://github.com/Microsoft/azure-pipelines-agent/issues/2043
Comment 2Alexander Bokovoy
2019-05-15 18:01:36 UTC
Yes, many CI providers pre-configure access to containers with sudo. In the case of Azure Pipelines, if you want to use containers directly from the pipeline definition, the container itself has to provide sudo. See https://github.com/microsoft/azure-pipelines-agent/issues/2043 for details.
Yeah, I linked to the Azure issue in the original description. Has IdM actually run into cases outsize of Azure where the lack of sudo in the images presents hurdles that users/customers can't overcome? The crux of the issue here is that it is relatively simply to include sudo in the base images, but that bloats the size further and size is extremely sensitive here.
Comment 4Alexander Bokovoy
2019-05-15 19:56:47 UTC
We don't ship IdM container in RHEL 8 yet.
However, I already stumbled upon this problem when setting up CI for FreeIPA on Azure where I use Fedora 30/31 base images. I had to use fedora-toolbox container image as a base to build packages as that one has sudo. Without it, my only option would have been to pull the original image and rebuild a container by adding sudo locally. Unfortunately, then I cannot specify container in Azure pipeline definition directly and would need to deal with it by talking to a container engine.
If there would be a similar UBI image with sudo, that would simplify work a lot by not requiring a special container rebuild just to make sudo available in the image.
I responded to the MS GitHub repo that we could consider adding a layered image at Microsoft someday to support this use case. Until then, I recommend users build a layered image on UBI, and push it to quay.io.
https://github.com/Microsoft/azure-pipelines-agent/issues/2043