Legacy Knowledge Base
Published Jun. 30, 2025

Liferay PaaS: Cannot add hotfix to the GitHub repository - Hotfix is larger than 100MB

Written By

Solyom Nagy-Györkös

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • The hotfix is so large that it is cannot be added to GitHub repository from local Liferay environment.
  • GitHub has 100MB limit and large file support would add more costs (if it would resolve it).

Environment

  • Liferay PaaS

Resolution

  1. The best way to resolve this use case is to create a file called Dockerfile.ext under Liferay folder.
    Everything in this file will be added at the end of the Dockerfile created by createDockerfile.

  2. In this Dockerfile the following line can be added, replacing XXXX for the hotfix to be installed: 
    RUN /opt/liferay/patching-tool/patching-tool.sh install hotfix-XXXX
    This way it will download the hotfix before the container gets up.

  3. (It is probable that running a newer Docker image already contains the newest patching tool, therefore the newest patching tool not necessary to be added, but stay alert to any errors regarding the patching tool.)

Did this article resolve your issue ?

Legacy Knowledge Base