Bug 107506 - [PATCH] systemd-units: Add "Condition=!container"
Summary: [PATCH] systemd-units: Add "Condition=!container"
Status: RESOLVED MOVED
Alias: None
Product: plymouth
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-07 08:23 UTC by Hans de Goede
Modified: 2018-08-07 09:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
[PATCH] systemd-units: Add "Condition=!container" (4.54 KB, patch)
2018-08-07 08:23 UTC, Hans de Goede 		Details | Splinter Review
View All

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.