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.

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

All this could potentially be solved with building a version and putting it in Quay.io. Going to close, deferred this bug..