Operating System CentOS

Install Alfresco Community Edition on AlmaLinux 9 or Rocky Linux 9 with Docker

Deploy Alfresco Community Edition on AlmaLinux 9 or Rocky Linux 9 using the official Docker Compose file, then lock down exposed ports and protect your data.

Alfresco Content Services Community Edition is the open source edition of the Alfresco document management platform, now developed by Hyland. This guide brings up a working Community Edition stack with Docker Compose on AlmaLinux 9 or Rocky Linux 9 (CentOS Stream 9 works the same way): the repository, the Share and Content App web interfaces, PostgreSQL, search and document transformation. CentOS 7 reached end of life in June 2024, and the all-in-one .bin installer that older tutorials download no longer exists, so both the operating system and the installation method have changed.

How Community Edition is distributed today

Alfresco stopped shipping the graphical Linux installer years ago. The Community Edition is published as container images, and the project's acs-deployment repository provides a ready-made community-compose.yaml for Docker Compose plus Helm charts for Kubernetes. No licence or registry account is needed for the Community images.

The Compose file currently starts these containers: the content repository, Share, Alfresco Content App, Control Center, Transform Core (LibreOffice, ImageMagick and PDF rendering in one image), PostgreSQL, ActiveMQ, Elasticsearch with a batch indexing job, Kibana, and a Traefik reverse proxy that publishes everything on port 8080.

Be aware of what Alfresco says about this method: the Compose files are intended for test and demonstration environments and are not presented as production-ready. Treat the result as an evaluation or small internal system unless you add your own backups, TLS and hardening.

Requirements

  • AlmaLinux 9, Rocky Linux 9 or CentOS Stream 9, 64-bit, with a user that has sudo rights.
  • Memory: the deployment documentation asks for at least 13 GB of free memory and recommends 16 GB for Docker. Containers exit without warning when memory runs out.
  • Several gigabytes of disk space for images, plus room for your documents.

Step 1: Install Docker Engine and the Compose plugin

Docker's RPM repository for CentOS is the one used on the RHEL 9 rebuilds:

sudo dnf -y install dnf-plugins-core git
sudo dnf config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
sudo dnf -y install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo systemctl enable --now docker

Confirm that both parts work:

sudo docker version
sudo docker compose version

Step 2: Get the deployment files

cd /opt
sudo git clone https://github.com/Alfresco/acs-deployment.git
cd /opt/acs-deployment/docker-compose

The master branch only references released product versions. For a reproducible setup, list the tags with git tag and check out the newest release tag before continuing. The image versions that will run are visible in the file itself:

grep image: community-compose.yaml

Step 3: Start Alfresco

sudo docker compose -f community-compose.yaml up -d

The first run downloads all images and takes a while. The repository needs a few minutes after that to create its database schema. Watch progress with:

sudo docker compose -f community-compose.yaml ps
sudo docker compose -f community-compose.yaml logs -f alfresco

Wait until the alfresco and share containers report healthy.

Step 4: Open the firewall and log in

All web interfaces are served by the proxy container on port 8080:

sudo firewall-cmd --permanent --add-port=8080/tcp
sudo firewall-cmd --reload
InterfaceURL
Sharehttp://203.0.113.20:8080/share
Content Apphttp://203.0.113.20:8080/aca
Control Center (users and groups)http://203.0.113.20:8080/control-center
Repository and REST APIhttp://203.0.113.20:8080/alfresco

The initial account is admin with the password admin. Change it immediately in Share under your user profile.

Step 5: Lock down what the Compose file exposes

The stock file is written for a developer workstation and publishes internal services on the host as well: PostgreSQL (5432), Elasticsearch (9200, 9300), Kibana (5601), the ActiveMQ console and brokers (8161, 5672, 61616, 61613), the transform service (8090) and the Traefik dashboard (8888). Docker inserts its own packet filter rules, so ports published by containers can be reachable even when firewalld does not list them.

On a server with a public address, edit community-compose.yaml and commons/base.yaml and either delete the ports: entries of those services or bind them to loopback, for example "127.0.0.1:5432:5432". Only the proxy's 8080 has to be reachable, and it should sit behind a TLS-terminating reverse proxy (Nginx, Apache or Caddy on ports 80 and 443) rather than being used over plain HTTP. Apply the change with:

sudo docker compose -f community-compose.yaml up -d

Data, backups and day-to-day operation

Stop and start the stack without losing anything:

sudo docker compose -f community-compose.yaml stop
sudo docker compose -f community-compose.yaml start

Do not use docker compose down casually. The stock file keeps the content store in an anonymous volume at /usr/local/tomcat/alf_data inside the repository container, and the deployment documentation states that down removes the containers and loses the data. Before you store real documents, map the content store and the PostgreSQL data directory to named volumes or host directories in the Compose file, and back up the two together: a PostgreSQL dump and a copy of the content store taken at the same time. The search index can be rebuilt from those.

To change repository settings, add -Dproperty=value entries to the JAVA_OPTS of the alfresco service. To upgrade, pull the newer deployment files, review the image tags and run up -d again after taking a backup. The full list of options is in the Docker Compose deployment documentation.

Frequently asked questions

Is there still a native installer for Linux?

No. The one-file installer that bundled Tomcat, PostgreSQL and LibreOffice was discontinued. The supported choices are containers (Docker Compose or Helm) or assembling the components yourself from the distribution archives on your own Tomcat and PostgreSQL.

Can I run it on a 4 GB server?

Not with this stack. The per-container memory limits in the Compose file add up to well over 8 GB, and the documentation gives 13 GB as the minimum. Lowering the limits makes containers restart under load.

What is the difference between Share and the Content App?

Share is the long-standing collaboration interface with sites, wikis and document libraries. The Content App is the newer Angular-based file interface. Both talk to the same repository, so you can use either or both.

Why does search return nothing right after the first start?

Indexing in this deployment is done by the batch indexing container against Elasticsearch. Check its output with sudo docker compose -f community-compose.yaml logs batch-indexing and the state of the elasticsearch container.

Share story:

Continue reading other guides on How VPS.