Just a general perspective commentary on the 2 options for installing 6.2 which might be a compelling reason why this question has been asked before...
Although the docker container is reasonably straightfoward which is initially great way to get an overview on 6.2 however since the documentation is in some cases segmented but really doesn't provide a clear manual install path as it's very summarized in points. The other thing is from reading within some of the forum threads, it seems to make it harder to complete changes, updates and fixes etc...
What I believe the user really would like to see is perhaps a walkthrough scenario in completing a manual install from begining to completion. In the end, I would think once there's a good walkthrough scenario example, it will be better suited to allow future updates and changes vs. just running in docker. Lastly, keep in mind that in previous older version like the 5.2 community release made it rather easy process in completing a standalone install since it was just 1 executable bin file which was the previous way someone was used to completing install.
Even when you look back at the 5.2 build and search around, there's plenty of step by step walkthroughs and even some videos showing the steps. Hence, this might be just worth mentioning since if you look in comparison, aside from the easy docker deployment, there's nothing much out there on a manual install scenario. It might be a nice thing to see and would help promote the 6.2 release as well
Thanks for your considered review of the installation process and documentation - there is a lot of work being done internally at the moment with regard to installation & deployment scenarios & technologies. With that in mind, the first Tech Talk Live of 2021 is on this subject. Perhaps you could attend and raise these points on the day?
Digital Community Manager, Alfresco Software. Problem solved? Click Accept as Solution!
However I wanted to share a recent enough example of someone who took some time to try and document the process of installing the required prerequesites, Tomcat and war files to complete a community install for 6.2 etc...
Given it's possible that this document might help but it's likely that issues will come up with this walkthru such as
this might only work with a very specific OS distro/build
If someone doesn't use the correct JRE build since the newer OS distros might have newer version of JRE so it's possible due to newer jre build that some serverlet components might not work because of deprecated code as often JRE can potentially update their code and the aflresco might require specific version of JRE (I'm suspecting it might matter)
Also just as much depending on a persons choice of DB used for setup, there is also specific version of java db connector and the parameter strings which may not always work properly (again some because of code deprecation)
I'm sure there's more things to add to this list but it's really intended to make a point and help to encourage vendor to make it easier. In the older 5.x days, It was simply a bin installer and a script walkthru which made it easy enough for almost anyone with a little knowledge to successfully get things running quickly. I've previously recommended the community edition to other before for 5.x because of it's simplicity to deploy however 6.2, standalone install is no longer that easy and some people I know don't want to just test PoC with the container platform. So it goes without saying,
Other suggestions as food for thought and maybe this could be for Aflresco themselves to consider in providing a prebuilt VM appliance (many vendors do this) already setup with the necessary stuff to allow someone to use for either just for community use purpose or providing to prospective customers who are evaluating the product based on small on premise build vs. container. Again this is merely feedback perspective but, it might be a good stepping stone
In my own experience, I know running the container version is much easier to deploy but having a reasonably robust document or even webinar like video demo showing customers a walkthrough on how it's done and some of the important caveats or point of interest to ensure a higher percentage of success as I'm sure some will shy away in trying alternate product.