Default installers (recommended)

Gluesync kits include platform-aware installers that deliver a ready-to-run environment in a single step. Pick your operating system during download and run the bundled installer to provision Docker or Podman (based on your selection), configure the Gluesync services, and apply the security prerequisites—no manual package installation required.

Why use the default installers?

Zero prerequisites – the installer ships with everything needed to bootstrap Docker Engine, Docker Compose or Podman, and the Gluesync stack.
Automated system validation – pre-flight checks verify CPU cores, RAM, disk space, and network connectivity before installation begins.
Consistent hardening – logging limits (100MB max size, 5 file rotation), TLS defaults, and health checks are enforced exactly as our production reference architectures.
Faster onboarding – scripting removes guesswork for trials and production rollouts alike.
Rollback friendly – the installer keeps backups of any system files it touches (e.g., daemon.json.backup) so you can revert quickly if something unexpected arises.

System requirements

The installers automatically verify these minimum requirements before proceeding:

CPU: 4 cores minimum (warning issued at exactly 4 cores)
RAM: 8 GB minimum
Disk space: at least 100 GB free recommended, 200 GB preferred
Network: Connectivity to .docker.io, .docker.com, and api.backoffice.molo17.com

How the workflow operates

Download/Request the Gluesync installation kit and choose the target platform (this also includes a 30 day trial license).
Run the commands provided within the Gluesync download page linked in the email you received after the kit request.
The installer performs pre-flight checks, validates connectivity, and installs the container runtime.
Docker or Podman is configured with logging rotation and security settings.
The installer prompts for your kit ID (32 hexadecimal characters from your download email).
Gluesync services are loaded and the Control Plane URLs are exposed.
Log in with the default credentials (admin/admin) and start building pipelines.

Platform-specific installers

Linux installer script

Entry point: docker-installer.sh (version 2.0)
Supported distributions: Fedora, RHEL, CentOS, Ubuntu, Debian, Amazon Linux 2023, SUSE Linux Enterprise Server (incubating), openSUSE
Container runtime: Currently defaults to Docker (Podman support temporarily disabled but available in code)
Installation location: /opt/gluesync
Features:
- Automatic distribution detection and package manager selection
- Docker Compose plugin installation (or standalone for Amazon Linux)
- Logging configuration with 100MB max size and 5-file rotation
- User group management for non-root Docker access
- Rootless Podman support with socket configuration (when enabled)
- CNI network configuration fixes for compatibility

If during the setup process the you have skipped the initial platform run or just want to run the platform manually, you can run the following command located within the Gluesync installation directory:

./run.sh

Windows Server installer

Entry point: docker-installer-windows.ps1 (version 1.3)
Requirements: Elevated PowerShell session (Run as Administrator)
Supported versions: Windows Server 2019 (with compatibility warnings) and Windows Server 2022+
Installation location: C:\Program Files\Gluesync
Features:
- Automatic Docker version selection (28.5.2 enforced for Server 2019)
- Windows Containers feature enablement
- Docker Compose installation
- Automatic service registration and startup
- Desktop shortcut creation for quick access
- Handles automatic reboots if required by Windows features
- Kit ID validation and download from MOLO17 servers

Windows Server 2019 support is deprecated due to end-of-life security concerns. Migration to Windows Server 2022 or newer is strongly recommended.

./run.ps1

macOS installer

Entry point: Download the macOS kit ZIP file and extract it
Installation: Run ./run.sh from the extracted directory
Requirements: Docker Desktop must be installed and running
Installation location: Current directory where the kit is extracted

Uninstalling Gluesync

Both Linux and Windows installers include companion uninstaller scripts that cleanly remove Gluesync and optionally purge the container runtime.

Linux uninstaller

Script: docker-uninstaller.sh
Location: Same directory as the installer
Usage:
```
./docker-uninstaller.sh [options]
```
Options:
- -f, --force – Skip confirmation prompts
- --purge-runtime – Automatically remove Docker/Podman packages and data
- -h, --help – Show usage information
What it does:
- Stops and removes all Gluesync containers and volumes
- Deletes /opt/gluesync directory
- Restores original Docker/Podman logging configuration
- Optionally removes Docker/Podman packages and data directories
- Disables systemd services

Windows uninstaller

Script: docker-uninstaller-windows.ps1 (version 1.2)
Location: Same directory as the installer
Requirements: Elevated PowerShell session

Usage:

.\docker-uninstaller-windows.ps1 [-Force] [-NoRestart]

What it does:
- Cleans up Docker containers and images
- Stops and unregisters Docker service
- Removes Docker binaries and data directories
- Removes Gluesync from C:\Program Files\Gluesync
- Removes desktop shortcut
- Optionally disables Windows Containers and Hyper-V features
- Handles automatic reboots if required

Kubernetes and Helm charts

Prefer Kubernetes? Every kit includes Helm charts that mirror the defaults used by our managed service. Follow the helm install flow documented in Kubernetes deployment to customize namespaces, storage classes, or ingress controllers while keeping parity with the default installer settings.

Need manual or DIY instructions?

Operations teams that must comply with hardened baselines can still follow the manual playbooks in DIY deployment guides. Those resources break down each container runtime configuration step, whereas this document remains the recommended path for fast, fully supported installs.