This doesn’t help people who now have a bare metal install now, data, database and config migration to those appliances isn’t always trivial, and they have various limitations as well, especially being not fully configurable, and the container engine brings further resource needs, complexity and inherently risks, like our Discourse broke down for a few minutes yesterday night after an upgrade because of: Daemon cannot start containers without apparmor · Issue #44900 · moby/moby · GitHub
Someone with limited experience to diagnose service startup issues, search for the right keywords or like me just tries apt install apparmor according to the error log, may be stuck for a longer time.
I don’t think that PHP 7.4 support can be re-enabled easily now, NC26 is in beta already, and reasonably from developer perspective the motivation is absolutely minimal. So I write this more to make you guys aware form end user perspective and about possible issues and topics like this (saw just now) to come up.
Let’s look and solve this forward. I’ll use the weekend to write some HowTo about the matter.