It's not going to make a meaningful difference in your threat model and it will cause a lot of hassle for extra configuration and broken docker images, so I wouldn't bother.
There is some nice tooling for transparent user name spaces coming down the pipeline in Kubernetes which will be a nice 0-effort security upgrade, but if you don't have the tooling, I would say it's not worth it.
If you need 10tb of storage, you could get 2x used 10tb hdds in raid 1 for $200, but 6x used 2tb nvme in raid 5 is only $600 and 100x faster. Both take up the same amount of space.
Being smug over the meanings of words that aren't ever actually used in a consistent way is even more American.
Um actually, Strawberries are not a berry, it's a Gameboy, not a Nintendo, and I lick toads. Can you go to the bathroom?
The only thing similar that I have experienced in Europe is the protected food name law, e.g. Champagne and Parmesan, but that's an EU cultural protectionism law that the US doesn't actually follow.
Then you'd probably swing your sword around and get it stuck in the wall and die. Rapiers and polearms are probably better in tight spaces against unarmored opponents. Polearms are just always better in general if you don't have sword training.
It's like comparing a shotgun to a AR-15 pistol. Sure, the pistol is more compact, has more power, and will put more rounds downrange, but they're all going to be in the ceiling if you haven't trained with it. The shotgun will be more effective.
Yes, and if you want custom configuration, you can include your configuration in-line in the same file that installs the http server and sets up systemd for it. Or you can even write your own module that drops configuration files in the same file.
Home-manager modules are modules that run stuff exclusively in ~, doing things like configuring browsers or dotfiles. As opposed to NixOS modules which configure system-level daemons.
It's not going to make a meaningful difference in your threat model and it will cause a lot of hassle for extra configuration and broken docker images, so I wouldn't bother.
There is some nice tooling for transparent user name spaces coming down the pipeline in Kubernetes which will be a nice 0-effort security upgrade, but if you don't have the tooling, I would say it's not worth it.
https://kubernetes.io/docs/concepts/workloads/pods/user-namespaces/