Hello! Apologies if this has already been asked. I’m trying to understand how to use the update lock to prevent updates. My current understanding (from Update locks | balena and Self-service updates | balena ) is that in a multicontainer application, creating the lockfile in any container at /tmp/balena/updates.lock should prevent reboots, application updates, and host OS updates, while supervisor updates are still allowed (since they do not require a reboot).
However, when I create the lockfile (using lockfile from procmail, as suggested by the Update Locks page), it prevents reboots and application updates, but OS updates still go through and ultimately reboot the device. Is this the expected behavior? Host OS version is 6.9.4+rev2 and supervisor version is 17.2.1 (though the versions have been slowly going up during testing).
Thanks for your help!