Canonical: https://molo17.com/blog/gluesync-docker-swarm-support/ Markdown mirror: https://molo17.com/blog/gluesync-docker-swarm-support/index.md Title: Gluesync on Docker Swarm: Swarm kit and Conductor · MOLO17 Description: Deploy Gluesync 2.3 as a Docker Swarm stack on Linux or Windows Server 2022 with the Swarm kit; Conductor 0.14.0 updates with automatic rollback. [← All articles](/blog/) Article # Gluesync now runs on Docker Swarm, on Linux and Windows Server 2022  6 Nov 2026 [Gluesync](/blog/?category=gluesync) 3 min read Deploy Gluesync 2.3 as a Docker Swarm stack on Linux or Windows Server 2022 with the Swarm kit; Conductor 0.14.0 updates with automatic rollback. Gluesync 2.3 now installs as a Docker Swarm stack. The new Swarm kit, available from [Get Gluesync](https://molo17.com/get-gluesync/), deploys a stack named `gluesync` on Linux (one node or several) or on a single Windows Server 2022 node. Gluesync Conductor 0.14.0, released on 30 October 2026, manages that stack: it lists, restarts and updates its services, with automatic rollback when an update does not become stable. If your team already runs Swarm, Gluesync now fits the tooling you know: `docker stack deploy`, `docker stack services` and `docker service logs`. ## What is in the stack The kit ships a `docker-stack.yml` with the image versions selected for your release, plus your licence and security files in its `shared` directory. The stack contains: - `reverse-proxy`: Traefik, publishing ports 80 and 443 (80 redirects to 443) - `gluesync-core-hub`: Core Hub and its web UI - `gluesync-chronos`: Gluesync Chronos - `prometheus`: metrics, served under `/prometheus` - `grafana`: dashboards, served under `/grafana` - `gluesync-conductor`: lists, restarts and updates the services of the stack Agents are added from Core Hub once the platform runs. Conductor adds each agent to `docker-stack.yml` and deploys it. ## Linux: one node or a whole swarm The Linux kit uses two node roles, and one machine can hold both. The **manager** holds the kit directory and runs Traefik and Conductor. The **data node**, labelled `gluesync.data=true`, holds all persistent data under `GLUESYNC_DATA_ROOT` (default `/var/lib/gluesync-swarm`) and runs Core Hub, Chronos, Prometheus and Grafana. Stateful services are pinned to the data node and use bind mounts, so a rescheduled task always finds its data. Backups stay simple: back up `GLUESYNC_DATA_ROOT` on the data node. Installation is three commands: ```bash docker swarm init # on the manager sudo ./prepare-host.sh # on the data node, in the gluesync-docker-swarm directory ./deploy.sh # on the manager that holds the kit ``` You need Docker Engine 23 or later with Swarm mode on every node, the Swarm ports open between nodes, and ports 80 and 443 free on the manager (or other ports set in `.env`). ## Windows Server 2022: Swarm with Windows containers The Windows kit runs every service on a single Swarm node, with `ltsc2022` images in process isolation. From PowerShell as Administrator, `.\prepare-host.ps1` checks the Windows build, the Containers feature and Docker, opens the firewall ports, pulls the images and creates the swarm. `.\deploy.ps1` deploys the stack. Use Windows Server 2022 with the latest cumulative update. The kit was tested on build 20348.5622. ## Updates with automatic rollback When you update a service from Platform updates in the Control Plane, Conductor in Swarm mode: 1. Leaves services already on the target image untouched. 2. Sets the new image with automatic rollback as the failure action. 3. Waits until all replicas have kept running for `UPDATE_VERIFY_SECONDS` (default 20). 4. Writes the new tag back to `docker-stack.yml`, so a later deploy keeps the update. If the new version does not become stable, the service goes back to its previous image and the stack file keeps the previous tag. Image download time does not count against the verify window, so large Windows images get the time they need. After an update, running the deploy script again leaves the updated services running. Conductor also switches release channel from alpha to beta or GA while keeping Swarm support, and the Conductor API is the same as with Docker Compose, so every Control Plane page works the same way. ## Get started - [Deploy Gluesync on Docker Swarm](https://docs.molo17.com/gluesync/latest/deploy-and-run/docker-swarm.html): requirements, node roles, Windows details and Conductor in Swarm mode - [Deploy and update Gluesync on Docker Swarm](https://docs.molo17.com/gluesync/latest/learn/how-to-deploy-gluesync-on-docker-swarm.html): the step-by-step guide - [Platform updates](https://docs.molo17.com/gluesync/latest/deploy-and-run/ota-updates.html) - [Conductor changelog](https://docs.molo17.com/gluesync/latest/gs-modules/conductor-changelog.html) Download the Swarm kit from [Get Gluesync](https://molo17.com/get-gluesync/) and run your pipelines on the orchestrator you already trust. [← Older article Gluesync now speaks Apache CouchDB, as a source and as a target](/blog/apache-couchdb-agent-gluesync-2-3-1-4/) ## Keep reading 1. [Gluesync Proactive resilience: introducing Gluesync’s Automatic Anomaly Detection New Automatic Anomaly Detection for Gluesync proactively identifies infrastructure issues and opens support tickets for you, ensuring your data pipelines stay resilient 24/7. Free. 10 Apr 2026](/blog/automatic-anomaly-detection-gluesync/) 2. [Gluesync Introducing Gluesync 2.2: elevating real-time data integration with a new plugin-based architecture and enterprise scalability Gluesync 2.2 introduces a new plugin-based architecture, reduced resource usage and a new Windows MSI installer. 6 Mar 2026](/blog/gluesync-2-2/) 3. [Gluesync Gluesync 2.1.7 released: Conductor brings agent orchestration and new Kubernetes support Discover Gluesync 2.1.7 introducing Conductor for automated agent orchestration, revamped Kubernetes support and improved Docker Compose deployment. 27 Oct 2025](/blog/gluesync-2-1-7-agent-orchestration-new-kubernetes-support/) [Back to all articles](/blog/) [More in Gluesync →](/blog/?category=gluesync)