Go to Docker Hub https://hub.docker.com/u/alfresco/ to see a list of images belonging to the alfresco user. Alternatively, access Docker Hub and search for alfresco (note that not all images are visible):
There are a number of Docker images that relate to Alfresco Content Services:
- alfresco/alfresco-share - the Share web interface (i.e. share.war) running on Apache Tomcat
- alfresco/alfresco-search-services - the Solr 6 based search service running on Jetty
- alfresco/alfresco-content-repository - the repository app (i.e. alfresco.war) running on Apache Tomcat
- alfresco/alfresco-activemq - the Alfresco ActiveMQ image
Alfresco Content Services provides a number of content transforms, but also allows custom transforms to be added. It's now possible to create custom transforms that run in separate processes from the repository, known as Transform Engines (i.e. T-Engines). The same engines may be used in the Community and Enterprise Editions of ACS. They may be directly connected to the repository as Local Transforms. Note that in the Enterprise Edition, the default option is to use them as part of Alfresco Transform Service, which provides more balanced throughput and scalability improvements.
See Custom Transforms and Renditions for more.
To build the alfresco/alfresco-content-repository image, Alfresco uses the Alfresco/acs-packaging GitHub project. This project doesn't include any deployment templates. The Alfresco/acs-deployment GitHub project contains deployment templates and instructions. It includes a Docker Compose script that's used to launch a demo, test, or PoC of Alfresco Content Services. You can customize this script, if you like, in order to run with different versions than those set by default (which are usually the latest versions).