Description of problem: When running in a container with plymouth installed, plymouth is started unnecessarily, and systemd prints warnings: [ OK ] Reached target Shutdown. Sending SIGTERM to remaining processes... Sending SIGKILL to remaining processes... Process 253 (plymouthd) has been been marked to be excluded from killing. It is running from the root file system, and thus likely to block re-mounting of the root file system to read-only. Please consider moving it into an initrd file system instead. Halting system. Container fedora-24 has been shut down. The warning might be something to fix even for non-container systems, but at least for container systems it makes sense to avoid starting plymouth altogether. Please add 'Condition=!container' everywhere were ConditionKernelCommandLine=!plymouth.enable=0 appears. Default installation should work in a container without any warnings.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Hi, Thank you for the bug report, I've written a patch for this and submitted it upstream: https://bugs.freedesktop.org/show_bug.cgi?id=107506 This should be in the next upstream release which should happen soon. Regards, Hans