Netdata autoupdate causes kernel, glibc, etc. to update?

It appears that Netdata’s auto-update mechanism can somehow trigger other non-Netdata-related updates.

I have Netdata installed on an Ubuntu 24.04 server, using the official Netdata repo as an apt source.

# cat /run/reboot-required
*** System restart required ***

# cat /run/reboot-required.pkgs
libc6
linux-image-5.15.0-112-generic
linux-image-5.15.0-113-generic
linux-image-5.15.0-116-generic
linux-image-5.15.0-117-generic
linux-image-5.15.0-118-generic
linux-image-5.15.0-119-generic
linux-image-5.15.0-121-generic
linux-image-5.15.0-122-generic
linux-image-5.15.0-124-generic
linux-image-5.15.0-125-generic
linux-image-5.15.0-127-generic
linux-base

I am not applying these updates.

How do I prevent the Netdata auto-update from updating other packages? (I want Netdata to update, but do not want it updating other packages!)

Hi, could you please elaborate on your observation that Netdata updates other packages? Why do you think so?

This file (/run/reboot-required) indicates whether the system requires a restart.

The /run/reboot-required mechanism is used when a reboot is needed to fully apply the changes introduced by package installation or upgrade.

So, you have already updated your system, and not updating Netdata will require a reboot.

Upon further investigation, it seems that APT::Periodic::Unattended-Upgrade "1" was inadvertently set via an errant Ansible run on this server, which made it appear like it was Netdata’s autoupdater causing this to happen.

Thanks for the quick reply — and my apologies for jumping to the conclusion that it was somehow Netdata auto-updates causing this!

1 Like