I wouldn't say it this way. Problem is the error message, not the modules. They won't install because they don't have a "default" install profile - which is not required. You can still use them as dependencies, or install packages manually.

Shim is special - it has only "master" stream - so dnf won't pick it up by default, as it always goes for "f26" stream.

Please describe "Some modules fail to install" as a "wrong dnf error message", not as wrong modules. The "default" install profile - used in "dnf install module" - is just optional.

Please document shim separately as there is a different reason for it not to install. This is because we don't have the system profile in place - dnf always goes for "f26".

Happy to merge when these two things are fixed.

Also, "installer" and "shim" modules are only useful when installing on a physical machine/VM. They have no use in the container - but that does not make them bad or anything. Do we want to document this as well?

Also, "base-runtime", "shared-userspace", and "perl" are almost always installed as dependencies - DNF just won't show that info.

It looks as if changes on the DNF and modules fronts have obsoleted this PR. Closing.