The update was meant to fix a situation where an attacker would somehow get grub onto a machine that was SINGLE booting windows and use grub to tamper with secureboot. this fix was meant to only apply in single boot situations where it should be entirely unexpected to see grub. as they said, something went seriously wrong.
I was thinking the meters with the metal probes that go through yeah. Wasn’t aware that could exacerbate the issue.
“At the root of the problem are cowboy traders (unlicensed tradesman/contractor) who apply the foam without a full survey or appropriate expertise – but because of lenders’ caution, this is affecting other homeowners who had similar work.” also “because surveyors are unable to inspect the roof timbers behind the layers [for moisture], mortgage lenders tend to issue blanket refusals on properties where any foam is present.” Maybe in the U.S. we just use wood moisture meters to check for moisture?
Docker takes a lot of the management work out of the equation as many of the containers automatically update. Manual updates are as simple as recreating a container with a new image instead of your local one. I would like to add try running Portainer (a graphical management interface for Docker). Breaking out the various options into a GUI helped me learn the ins and outs of Docker better, plus if you end up expanding to multiple docker hosts you can manage them all from one console. I have a desktop, a laptop, and a RPi 4b all running various dockers and having a single pane for management is such a convenience.
Now tell us the pixel response time.
this here is the real issue.