- Download the docker-compose.yml file by accessing the Content Services Download Trial page, which will give you a 30-day license.
- Save the file in a local folder.
-
Edit the file and change the following two services:
Add a # prefix to the Alfresco Content Repository and Alfresco Share Docker image locations so they are commented out, and add the Alfresco Governance image locations:
services: alfresco: #image: alfresco/alfresco-content-repository:23.x.x image: quay.io/alfresco/alfresco-governance-repository-enterprise:23.x.x mem_limit: 1700m
share: #image: alfresco/alfresco-share:23.x.x image: quay.io/alfresco/alfresco-governance-share-enterprise:23.x.x mem_limit: 1g
Replace the ACS versions (for example, ACS 23.1.1) with the compatible AGS versions (for example, AGS 23.1.1).
-
In a command prompt login to Quay using the following command (to open up
access to Enterprise Docker images):
$ docker login quay.io login against server at https://quay.io/v1/ Username: <Quay.io Credential Username> Password: <Quay.io Credential Password>
-
In the command prompt change directory to the location of the
docker-compose.yml file and deploy Governance Services
using the following command:
$ docker-compose up
This downloads the images, fetches all the dependencies, creates each container, and then starts the system. If you downloaded the project and changes were made to the project settings, any new images will be pulled from Quay before the system starts.
As an alternative, you can also start the containers in the background by running:
$ docker-compose up -d
-
Wait for the logs to complete.
... alfresco_1 | ... INFO ... [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"] alfresco_1 | ... INFO ... [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"] alfresco_1 | ... INFO ... [main] org.apache.catalina.startup.Catalina.start Server startup in 226026 ms
If you encounter errors whilst the system is starting up:
- Stop the session (by using CONTROL+C).
- Remove the container (using the --rmi all option). For
example:
$ docker-compose down --rmi all
- Try allocating more memory resources, as advised in docker-compose.yml. For example, in Docker, change the memory setting in Preferences (or Settings) > Advanced > Memory, to at least 6 GB. Make sure you restart Docker and wait for the process to finish before continuing.
- Go back and retry the deployment.
Note: Although 16 GB is the required minimum memory setting, keep in mind that 6 GB is much lower than the required minimum, and may need to be adapted for your environment. -
Open your browser and check everything starts up correctly:
Share: http://localhost:8080/share
Final step before you can start with Records Management
is to create the Records Management
site.