Installers changelog

Version history for the Gluesync kit installers. Each section is one installer. Versions and dates below are taken from the installer scripts, the public launcher and installer repository, and the Installers bullets in the Gluesync release notes. The public repository does not tag installer releases, so a calendar date appears only when a Gluesync release note or a dated commit records the change.

Current versions

These are the versions documented on this page. MSI ProductVersion and docker-installer-windows.ps1 $ScriptVersion are 1.3.2 for installer kit 1.3.2. The Linux docker-installer.sh welcome banner is still 2.0; its 1.3.2 changes are listed under that banner. Offline and uninstaller strings below are the values on installer main. The 2.3 kit page is a walkthrough and does not repeat the numbers.

Installer Version Notes

gluesync-platform-installer.msi

1.3.2

Released: October 11, 2026. ProductVersion for kit 1.3.2. Installer main still defaults to 1.3.1.

docker-installer.sh (Linux)

2.0

Welcome banner. Unchanged for kit 1.3.2; unattended and RAM changes ship with that kit.

docker-installer-windows.ps1

1.3.2

$ScriptVersion for kit 1.3.2. Installer main still prints 1.3.

docker-installer-linux-offline.sh

1.0

Banner version on main. Not listed on the 2.2 kit page.

docker-installer-windows-offline.ps1

1.0

$ScriptVersion on main. Not listed on the 2.2 kit page.

docker-uninstaller.sh

2.0.0

$SCRIPT_VERSION on main. The 2.2 kit page does not print a Linux uninstaller version.

docker-uninstaller-windows.ps1

1.2

$ScriptVersion on main; also listed on the 2.2 kit page.

Windows MSI (gluesync-platform-installer.msi)

The MSI targets Windows Server 2019, 2022, and 2025 only. It installs native Windows containers with process isolation. It does not support Windows 10 or Windows 11 client editions, Linux containers, or WSL2.

The current MSI version is 1.3.2. The default ProductVersion on installer main is still 1.3.1 (scripts/build-windows-installer.ps1). The kit installer page has never listed an MSI version. The MSI itself was introduced with Gluesync 2.2.0 (Released: March 5, 2026). No separate MSI tag or calendar date for 1.3.0 is recorded in the public repository.

1.3.2

Released: October 11, 2026

  • After a successful install, the online MSI sends an install-success confirmation. The offline Windows installer does not;

1.3.1

Released: October 11, 2026

  • Correct handling of the Windows "restart required" result (exit code 3010). The installer no longer hides that result;

  • After the reboot, the install resumes automatically as a SYSTEM startup task. No logon is required. This replaces the previous RunOnce resume;

  • Writes a status file at %ProgramData%\MOLO17\Gluesync\Installer\status.json. The result values and the resume task exit codes are listed below;

  • Silent installs start the platform in the background. Setup-wizard installs still open the visible launch window for the installing user;

  • A retry resumes from the failed step. It does not reinstall from the beginning;

  • Copying the Docker binaries no longer fails when Docker is already running;

status.json results

result Meaning

InProgress

The feature install, Docker setup, or platform launch is still running.

PendingReboot

The first install stage is done and Windows needs a restart. The SYSTEM task continues at startup.

PendingUserLaunch

Setup-wizard installs only. Docker setup is done. The launch window opens at the installing user’s next sign-in, or immediately if that user is already signed in.

Succeeded

Docker setup is done, the platform launch exited 0, and at least one container is running.

Failed

The install did not finish. See message, lastExitCode, and the logs under %ProgramData%\MOLO17\Gluesync\Installer\logs. While failures remain below the retry limit, the next pass retries only the failed step.

Resume task exit codes

These are the exit codes from the SYSTEM resume task (gluesync-resume.ps1).

Code Meaning

0

Silent: succeeded. Setup-wizard: handed over to the user launch window (PendingUserLaunch). The resume task is removed.

3010

The restart has not happened yet. The task is kept.

1618

Windows Installer was busy. The task is kept.

40

The Docker setup stage of the MSI failed. Retried on the next pass, up to three failures.

50

Silent: the platform launch failed. Only the launch is retried.

55

Silent: the launch exited 0, but no container was running. Retried.

56

Setup-wizard: the user launch task could not be registered (Failed).

60

The retry limit (three failures) was reached (Failed). The task is removed.

70

Installer state or the cached MSI is missing (Failed).

75

Another resume task is already running. Status and the failure count are left unchanged.

90

Unexpected error in the resume task (Failed). Counted as a failure and retried.

docker-installer.sh (Linux)

2.0

Current welcome-banner version. The banner was not bumped for installer kit 1.3.2. The public repository does not tag script releases. The following user-facing changes landed while this banner version was current.

Installer kit 1.3.2

Released: October 11, 2026

These changes ship with installer kit 1.3.2. The welcome banner is still 2.0.

  • After a successful install, the online script sends an install-success confirmation. The offline Linux installer does not;

  • The install is blocked when the host has less than 4 GB of RAM, and warns when RAM is between 4 GB and 8 GB;

  • Unattended installs are supported with these environment variables (from the script header):

    • GLUESYNC_KIT_ID — the 12-character hexadecimal kit ID from the download email. Skips the kit ID prompt. An invalid value exits 26;

    • GLUESYNC_START — y or n for "start Gluesync now?". Without a terminal the default is n;

    • GLUESYNC_NONINTERACTIVE — set to 1 to never prompt, even when a terminal is available;

    • GLUESYNC_SETUP — y or n for "proceed with Gluesync setup?". Without a terminal: y when GLUESYNC_KIT_ID is set, otherwise n;

Earlier changes under banner 2.0

  • Added AlmaLinux support (Gluesync 2.2.3.0, Released: March 23, 2026);

  • Added Oracle Linux support (Gluesync 2.2.2.0, Released: March 19, 2026);

  • Stronger error handling and logging for endpoint reachability (Gluesync 2.2.2.0, Released: March 19, 2026);

  • Added Rocky Linux support (6f8563fb, May 8, 2026);

  • Installation continues when the Docker registry is unreachable, instead of blocking (d42f6455, May 4, 2026);

  • Allocates a 10 GB swap file during setup (e04fd775, June 22, 2026);

docker-installer-windows.ps1

1.3.2

Released: October 11, 2026

$ScriptVersion is 1.3.2 for installer kit 1.3.2.

  • After a successful install, the online script sends an install-success confirmation. The offline Windows installer does not;

  • The install is blocked when the host has less than 4 GB of RAM, and warns when RAM is between 4 GB and 8 GB;

  • Docker Compose download tries Invoke-WebRequest first, then BITS, then curl.exe. The downloaded file must run as docker-compose, or the install stops;

  • The script reports success only when the platform is running: run.ps1 exited 0 and the containers are up;

  • Named fatal errors print GS-RUN-<CODE> and exit with the codes below;

Fatal exit codes

These codes are defined in docker-installer-windows.ps1.

Code Name Meaning

21

COMPOSE_DOWNLOAD_FAILED

Docker Compose download failed, or the downloaded file does not run.

22

KIT_DOWNLOAD_FAILED

Kit zip download failed.

23

KIT_EXTRACT_FAILED

Kit zip could not be extracted.

24

KIT_INVALID

Kit has no folder for this platform.

25

KIT_COPY_FAILED

Copying the kit into the install folder failed.

30

RUN_SCRIPT_MISSING

run.ps1 is missing.

31

START_FAILED

run.ps1 exited non-zero.

32

CONTAINERS_NOT_RUNNING

run.ps1 exited 0, but the platform containers were not running.

1.3

Previous $ScriptVersion on installer main. No installer-specific calendar date is recorded. The following user-facing changes landed while this script version was current.

  • Stronger error handling and logging for endpoint reachability (Gluesync 2.2.2.0, Released: March 19, 2026);

  • Windows Server 2019 support, with Docker 28.5.2 enforced on that release (8fbcc6f7, March 1, 2026; ccf07728, March 2, 2026);

Offline installers

Linux: docker-installer-linux-offline.sh (banner v1.0). Windows: docker-installer-windows-offline.ps1 ($ScriptVersion 1.0). Neither script has a later version string on main. The offline installers do not send an install-success confirmation.

1.0

  • Linux offline installer available as early access (Gluesync 2.2.2.0, Released: March 19, 2026);

  • Linux offline installer generally available, including the dependencies needed to run Gluesync and offline updates (Gluesync 2.2.3.0, Released: March 23, 2026);

  • Windows offline installer available (Gluesync 2.2.3.0, Released: March 23, 2026);

  • Offline installers accept versioned platform archives named by architecture and prefix, not only the unversioned alias (7b876155, September 6, 2026);

Uninstallers

History for the uninstallers is thin. The public repository has no version tags, and the Gluesync release notes do not list uninstaller-specific bullets. The versions below are the strings in the scripts on main.

2.0.0

docker-uninstaller.sh. Current $SCRIPT_VERSION. The 2.2 kit page documents the script and its options (--force, --purge-runtime) but does not print this version. No dated user-facing changelog is recorded.

1.2

docker-uninstaller-windows.ps1. Current $ScriptVersion, also listed on the 2.2 kit page. No dated user-facing changelog is recorded.