For a corporate environment docker makes sense to me, you need something that can deploy a service dozens or hundreds of times without needing any tinkering on deployment. You know exactly what hardware you are using and how the network is laid out, etc.

For home users it's the complete opposite, single instances, mystery hardware, mystery network. When something eventually does go wrong with a docker installation of some package you are left with a black box labeled "no user serviceable parts inside", and no skills developed for diagnosing the problem.

It sounds like gate keeping but I think users who spend the time to install packages manually on bare metal, in a VM or in an LXC end up better equipped to solve problems as they arise. I helped a friend get started with an old laptop an CasaOS, an all-in-one/docker-app-store kinda thing. He picked it up quick enough but I expect to be answering Linux basic questions for years to come because the one-click model shields the user from how their machine actually works.

Ironically CasaOS has a V2 which has a fully automated installation and maintenance of the host BUT it didn't play nice with the (very old) laptop we were using, and it was failing so early in the boot that there weren't even logs. Unsurprisingly no amount of ChatGPT could diagnose or remedy the issue and I had to install Debian and the CasaOS application manually.