How does this approach not require them to agree to the ToS/EULA mentioned earlier in the post?
They spined up an VM in some service that started an red hat image with the required license already in place for that image..
it is the vm provider that is bound by the EULA, not RockyLinux..
They are bound by the ToS for the VM provider they are using, that does not prevent them to get the sources from Red Hat..
Seems pretty clear IBM is hostile to anyone using RHEL source to repackage an OS from, so anyone using a RHEL derivative is putting themself at risk.
Time to start using Debian.
Using the UBI images and public cloud instances does seem like a clever way to handle that.
here's hoping that red hat don't modify dnf to require some kind of key to get source code from the default repo, as stupid as that would be.
but some cloud providers offer vm with the license already in place, they pay the license in embed the cost in the vm price.. so the cloud provider that is bound by the eula..
