Docker-compose is a orchestration tool that wraps around the inbuilt docker functions that are exposed like “docker run”, when teaching people a tool you generally explain the base functions of the tool and then explain wrappers around that tool in terms of the functions you’ve already learned.

Similarly when you have a standalone container you generally provide the information to get the container running in terms of base docker, not an orchestration tool… unless the container must be used alongside other containers, then orchestration config is often provided.

Not necessarily, I’m using Pop!OS but my workplace AzureAD SSO mandates Edge on Linux so you’re not safe.

Doesn’t surprise me at all, the company I work for has gone all in with AzureAD SSO and that will only work on Edge (edge supplies info for the MS asset verification software that constantly eats my CPU) so now we can’t use anything other than Edge for any internal service and need to develop for Edge if we are writing an internal tool.

Personally I always use containers unless there is a good reason to use a VM, and those reasons do exist. Sometime you want a whole, fully functional OS complete with custom kernel, in that situation a VM is a good idea, sometimes a utility only comes packaged as a VM.

But absent of a good reason, containers are just better in the majority of cases

I would hope this would be obvious to anyone. If your client can highlight which posts you have upvoted in the web and app UI then the fact that your user specifically upvoted that post must be recoverable from the instance server and thus must be recoverable by the instance admins. I would not expect anything different.