Don't run /usr/lib/update-notifier/update-motd-hwe-eol in containers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* Information of HWE kernels are shown in containers despite this information is useless most of the time since containers use the host systems' kernels.
* The check for HWE kernels is noticably slow OTOH, taking around 0.2s on my intel i5 laptop.
[Test Case]
* Run the script in a container to see it being shortcut:
$ bash -x /usr/lib/
+ '[' '' = --force ']'
+ type systemd-detect-virt
+ systemd-detect-virt -q -c
+ exit
* Run the script in a VM of without virtualization to see it still taking long time to execute:
$ time /usr/lib/
real 0m0.241s
user 0m0.170s
sys 0m0.073s
[Regression Potential]
* The fix is very simple there is no expected regression.
This bug was fixed in the package update-notifier - 3.192.27
---------------
update-notifier (3.192.27) focal; urgency=medium
* Notify user about stale updates information in motd (LP: #1842159) update- notifier/ updates- available world-readable motd-hwe- eol: Run as a regular user without printing errors motd-hwe- eol: Shortcut script when running in a container. motd-fsck- at-reboot: Shortcut script when running it as
* Make /var/lib/
(LP: #1844704)
* data/update-
(LP: #185527)
* data/update-
There is no point in checking the HWE stack in a container since upgrading
it would not affect the host system. (LP: #1855290)
* data/update-
a regular user (LP: #185527)
-- Balint Reczey <email address hidden> Thu, 05 Dec 2019 15:02:52 +0100