It is not a mandatory transition. It is our recommendation, because, as most who have attempted it have found, the pre-requisites required to install the environment we need now are at the point where it is arduous to configure. As such, there’s a very high chance that people going down that route will hit issues with slight variations in their configuration. This has been 100% born out over the past few weeks.
I’m sorry you find it confusing. Lets look at it step by step. The instructions take you to the Install Docker page of the CMS manual (http://xibo.org.uk/manual-tempel/en/install_docker.html), which links you directly to this page:
Install Docker Engine | Docker Docs
The top table on that page links to detailed instructions for each distribution of Linux. It’s about 1 screen-full down.
Likely you’re using an old version of Docker Compose. Our install guide above links to you the releases page for the latest version, which explains in detail how to install it (and yes, that is as simple as downloading it to /usr/local/bin - no hoping required).
The Docker daemon starts automatically at boot, and the containers we provide start automatically unless you specifically modify them to prevent that.
Simply untrue. Docker containers have virtually zero overhead (when we’re talking about running on a Linux host). They run natively, on the same kernel as the host, simply utilizing the cgroups functionality in the kernel to ensure isolation, with no virtualization overhead.
Here’s a link to an excellent research paper from IBM on container overhead, in which their finding is that ‘Docker is nearly identical to Native performance’. Given the added security benefits (if the CMS were somehow compromised, then an attackers access is limited to the container only and not to your host machine) then I think it’s worthwhile.
Same place every single previous release we’ve put out on Github can be found:
The structure differs for very good reason. 1.8 CMS uses the Slim framework and adheres to various coding standards to improve security. Those include not putting third party library files in web-servable locations.
We do offer a basic overview in the manual. It’s broadly the same as it was before - with the exception that you’ll need to get the ZMQ PHP libraries installed, and change your webserver root to point to the web directory, rather than the root above.
We’re not going to prevent anyone doing that. All we’ve said is that if you hit issues with a custom installation, that because we don’t know the environment you’re using, we may not be able to offer you free support for it. I don’t think that’s unreasonable or unfair.
You’ve not offended me, but it has taken me some time to go through your message and address your points - most of which have already been discussed in the past few weeks. We’ve tried very hard to make the transition to Docker simple for people, because in the long run, a manual install will become increasingly difficult to maintain. I produced a step by step guide for Ubuntu 16.04 which again is linked from the manual. You could have followed that and not had any Googling to do!