Where is the Linux installer?

Every doc I read it says “Download Lucee Linux Installer” but on the download site there is only a Windows installer and a link to a Docker repository.

Where is the Linux installer? Can Lucee be installed without Docker on Linux?

OS: Linux Alma/RHEL
Java Version: x
Tomcat Version: x
Lucee Version: x

Steve, while we await an official answer (or pointer to some discussion on the matter), I can note at least that recent past “release”-level installers have offered a Linux one. For instance, just two point releases ago (picking from the drop down on the installer page), there’s specifically:


And once you install that one, you could of course upgrade it to 5.3.10 within the admin or otherwise.

I realize you may have looked at the current and previous point-release and, not seeing any, wondered somehow if there weren’t any Linux installers. Hope the above helps.

And granted, it’s not the single step one could want to be installing 5.3.10 on Linux, but at least it’s a solution while awaiting a Linux installer for 5.3.10. I suspect we’ll hear an explanation for that delay.

Before someone may say, “or you could just use commandbox”, he could also use the Lucee Docker image (as he noted), or the Lucee Express approach, or the war, and so on. ;-} There are lots of ways people can choose to implement Lucee, like ACF. He’s asking specifically (and understandably) about a Linux installer.

That said, I have wondered if there’s been consideration to adding a link to Commandbox at the top of the download page, like there is for the dockerhub link.


The latest kernel versions break the linux installer, or rather the linux installer is broken on the latest versions of the linux kernel.

As above, download the previous version and then upgrade.

Yes, you’re not going mad. The download interface is a bit odd.

You are looking for a production-ready stable Lucee release, so you want to find a Linux installer for Release-grade downloads:

• Under “Release”, navigate through the version dropdown until you find a release that offers a “Linux (64b) Installer”. At time of writing, that’s
wget the .run file to your Linux /tmp folder, set its permissions to executable and run it, as below:—

$ cd /tmp
$ wget https://cdn.lucee.org/lucee-
$ chmod +x lucee-
$ ./lucee-

Hope this helps.

Screenshot 2023-02-07 at 13.59.22

Screenshot 2023-02-07 at 13.59.58


I know the Lucee dev team tried to get certain things of the installer working smoother lately, e.g. enhancing the Java Version identification on the machines OS. Looks like an easy task, but it isn’t (especially when testing it on the various existing Linux flavours). By the way, the Lucee dev team isn’t the creator of the installer (it was handed over to/forked by the Lucee Team not so long ago), so the installer deployment is a task that still is pretty new. I’m sure the installer will be published ASAP.

The good news is, that you still can use an older installer version to install the latest stable Lucee version, just like @harryf thankfully showed and then upgrade the Lucee.jar, just like described in the Note section in the download and installing guide.

This workaround is likely not the satisfying answer you are expecting, but at this time, its the best we can get.

I just built and posted the linux installer for


help wanted with updating and improving the linux installer, linux n shell scripting isn’t my forte




if [ ! -f install-lucee.tar.gz ]; then
echo “install-lucee.tar.gz not found. Do you want to download it now? [1 for Yes/0 for No]:”
read download_choice
if [ $download_choice -eq 1 ]; then
wget https://github.com/example/version/install-lucee.tar.gz
echo “Exiting script. Please download install-lucee.tar.gz and run the script again.”
exit 1

echo “Do you want to use the default directory ($default_dir)? [1 for Yes/0 for No]:”
read choice

if [ $choice -eq 0 ]; then
echo "Enter the destination directory: "
read dest_dir

if [ ! -d $dest_dir ]; then
echo “$dest_dir does not exist. Creating directory…”
mkdir $dest_dir

tar -xf install-lucee.tar.gz -C $dest_dir

echo “Untar operation completed successfully.”


if [ -f $lucee_conf ]; then
echo “Moving lucee.conf to /etc/httpd/conf.d”
sudo mv $lucee_conf /etc/httpd/conf.d
echo “$lucee_conf not found.”

If I can find out exactly what lines are touched in Tomcat, (Which I am looking at anyways) I am looking to reverse build a RPM for RHEL clones and a deb for Debian clones. The above script works on RHEL Clones, with little if any modification.

Once fully tested, we can use CFEXECUTE to build the RPM file like so.

<cfset rpmName = "Lucee">
<cfset rpmVersion = "1.0">
<cfset rpmRelease = "1">
<cfset rpmSummary = "LUCEE RPM">
<cfset rpmInstallDirectory = "/opt/lucee">
<cfset rpmSourceFile = "lucee.tar.gz">
<cfset rpmLicense = "GPLv2">
<cfset rpmReadme = "/path/to/readme.txt">
<cfset rpmConfigFile = "lucee.conf">
<cfset rpmConfigFileDirectory = "/etc/httpd/conf.d">

<cfexecute name="rpmbuild" arguments="-ba --define '_topdir /tmp/rpmbuild' --define 'name #rpmName#' --define 'version #rpmVersion#' --define 'release #rpmRelease#' --define 'summary #rpmSummary#' --define '_rpmdir #rpmInstallDirectory#' --define '_srcrpmdir #rpmSourceFile#' --define 'license #rpmLicense#' --define 'readme #rpmReadme#' --define 'config #rpmConfigFile#' --define 'config_path #rpmConfigFileDirectory#' /tmp/rpmbuild/SPECS/#rpmName#.spec" timeout="600">
1 Like