Bug 107506

Summary:	[PATCH] systemd-units: Add "Condition=!container"
Product:	plymouth	Reporter:	Hans de Goede <jwrdegoede>
Component:	general	Assignee:	Ray Strode [halfline] <rstrode>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Attachments:	[PATCH] systemd-units: Add "Condition=!container"

Description Hans de Goede 2018-08-07 08:23:44 UTC

Created attachment 140991 [details] [review]
[PATCH] systemd-units: Add "Condition=!container"

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 

It makes little sense to start plymouth in contains, so add
'Condition=!container' everywhere where
ConditionKernelCommandLine=!plymouth.enable=0 appears to disable plymouth
in containers.

Also see https://bugzilla.redhat.com/show_bug.cgi?id=1337611

Comment 1 GitLab Migration User 2018-08-07 09:26:24 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/plymouth/plymouth/issues/27.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.