systemd-container should only be used within docker images, it should never be used on bare metal systems.
I'm not aware of any installer changes necessary for this. The main thing we need to prevent is anaconda somehow seeing systemd-container in the yum repositories used for regular installations.
I think it's in RHEL Extras, so as long as the installation target doesn't include that, Anaconda should be fine.
Oh, but maybe this is about the opposite use case, where someone was hitting issues building a Docker container using ImageFactory (which uses Anaconda)?
There's a bug in --dirinstall that needs to be fixed (I'll attach a patch). With that fix I've tested a minimal kickstart using fakesystemd or systemd-container, and as long as you don't include kickstart commands that trigger calls to systemctl a -anaconda --dirinstall --text --kickstart=... works fine.
Don't include firstboot or services and it will work fine. If there are specific problems, please add them to this bug and I'll take a look at them.
Created attachment 939010 [details]
patch so --dirinstall will work
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.