liferay/cms-standalone repository overview

⁠Tags

For tags⁠ that follow the format {version}-d{image version}-{date}, version denotes the version of Liferay CMS, image version denotes the version of the Liferay Docker⁠ scripts that built the image, and date denotes the date when the Docker image was made.

Tags⁠ that follow the format {version} always point to the latest tag that follows the format {version}-d{image version}-{date}.

Liferay CMS versions end with -cms-standalone, for example 2026.q4.0-cms-standalone.

The CMS images come with a 30 day trial license. Older images will be regularly deleted and new images with a new 30 day trial license will be made available.

⁠Running

To start Liferay CMS, replace {tag} and execute:

docker run -it -p 8080:8080 liferay/cms-standalone:{tag}

For example:

docker run -it -p 8080:8080 liferay/cms-standalone:2026.q4.0-cms-standalone

The -it argument allows you to stop the container with CTRL-C. Otherwise, you have to use docker kill {containerId} to stop the container.

The -p 8080:8080 argument maps the container's port 8080 with the host's port 8080 so that you can access Liferay CMS from a browser.

⁠Environment Variables

You can tune the default JVM parameters by setting the environment variable LIFERAY_JVM_OPTS.

You can customize the behavior of Liferay CMS via environment variables that map to portal.properties. For example, if you want to provide only English and Portuguese, you could create a portal-ext.properties with the entry:

locales.enabled=en_US,pt_BR

Or, you could set the environment variable:

LIFERAY_LOCALES_PERIOD_ENABLED=en_US,pt_BR

Each property's respective environment variable is documented in portal.properties⁠. Search for the text Env:.

Environment variables take precedence over portal.properties.

⁠File System

Docker containers are transient. Whenever you reboot a container, all changes on its file system are lost.

To quickly test changes without building a new image, map the host's file system to the container's file system.

Start the container with the option -v $(pwd)/xyz123:/mnt/liferay to bridge $(pwd)/xyz123 in the host operating system to /mnt/liferay on the container.

Files in the host directory $(pwd)/xyz123/files are also available in the container directory /mnt/liferay/files and will be copied to /opt/liferay before Liferay CMS starts.

For example, if you want to modify Tomcat's setenv.sh file, then place your changes in $(pwd)/xyz123/files/tomcat/bin/setenv.sh and setenv.sh will be overwritten in /opt/liferay/tomcat/bin/setenv.sh before Liferay CMS starts.

⁠Scripts

All scripts in the container directory /mnt/liferay/scripts will be executed before Liferay CMS starts. Place your scripts in $(pwd)/xyz123/scripts.

⁠Deploy

Copy files to $(pwd)/xyz123/deploy on the host operating system to deploy modules to Liferay CMS at runtime.

⁠About

Images are built on Ubuntu with Azul Zulu JDK 21. More information can be found in the Dockerfile at https://github.com/liferay/liferay-docker⁠.

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.