Gluesync Conductor

Gluesync Conductor is a container management platform that provides a comprehensive RESTful API for managing Docker containers, with specialized integration for Gluesync agent orchestration and lifecycle management within containerized environments.
This project is Open Source
Overview
Gluesync Conductor serves as the orchestration layer for Gluesync deployments by providing a centralized API for container management. It enables seamless agent deployment, configuration, and monitoring through integration with the Gluesync Core Hub, offering a streamlined experience for managing complex data pipeline infrastructures in containerized environments.
Built with Node.js and designed for flexibility, Conductor provides consistent RESTful API responses and supports advanced container operations including version management, persistence tracking, and automated updates.
Key Features
-
Container Management API
-
Complete RESTful API for Docker container operations
-
Container listing with detailed configuration and status information
-
Add, update, and remove containers programmatically
-
Container restart and image pulling capabilities
-
-
Agent Orchestration
-
Seamless integration with Gluesync Core Hub Web UI
-
Automated agent deployment from pipeline wizard
-
Dynamic agent provisioning based on pipeline requirements
-
Version checking and update management for containers
-
-
Configuration Management
-
Docker label-based container identification and tracking
-
Persistent container configuration through Docker Compose
-
Environment variable management and port mapping
-
Volume mounting and network configuration
-
-
Gluesync SDK Integration
-
Direct connection to CoreHub for advanced orchestration
-
License and security configuration management
-
Automatic service discovery and connection handling
-
UDP port range configuration for CoreHub communication
-
-
Monitoring & Operations
-
Real-time container status and health monitoring
-
Detailed logging and error handling
-
Container lifecycle management and persistence tracking
-
Support for multiple container runtimes (Docker, Podman)
-
Installation & prerequisites
System requirements
-
Node.js: Version 16 or higher
-
Container Runtime: Docker and Docker Compose (or Podman)
-
Package Manager: Yarn
Quick start
# Install dependencies
cd packages/gluesync-conductor
yarn install
# Start the service
PORT=50015 yarn dev
Environment configuration
For Gluesync SDK integration, configure the following environment variables:
-
GLUESYNC_LICENSE_FILE: Path to license file (default:/opt/gluesync/data/gs-license.dat) -
GLUESYNC_SECURITY_CONFIG: Path to security config (default:/opt/gluesync/data/security-config.json) -
COREHUB_UDP_PORT_RANGE: Port range for discovery (default:1718-1727, recommended:1717-1727)
API endpoints
Conductor provides a comprehensive REST API for container management:
Container operations
-
GET /containers: List all containers with detailed information
-
GET /containers/id: Get specific container configuration
-
POST /containers: Add new containers to the system
-
PUT /containers/id: Update existing container configuration
-
POST /containers/id/restart: Restart a container
-
POST /containers/id/pull: Pull latest container image
Docker labels & identification
Integration with Core Hub
Conductor integrates deeply with the Gluesync Core Hub to provide:
-
Web UI Integration: Direct agent deployment from pipeline creation wizard
-
Status Synchronization: Real-time agent status updates in Core Hub interface
-
Configuration Management: Centralized agent configuration through Web UI
-
Security Coordination: SSL certificate management and validation
-
Service Discovery: Automatic agent registration and discovery
Container platform support
Best practices
-
Version Management: Regularly check for and apply container updates
-
Resource Allocation: Configure appropriate CPU and memory limits
-
Persistence: Ensure critical containers are properly persisted
-
Monitoring: Implement logging and monitoring for container health
-
Security: Use SSL/TLS for API communications in production
-
Backup: Maintain backups of Docker Compose configurations
Troubleshooting
Common issues
-
Connection Failures: Verify Docker daemon accessibility and API connectivity
-
Version Conflicts: Check container image versions and compatibility
-
Resource Constraints: Monitor system resources and container limits
-
Network Issues: Validate network configuration and port mappings
-
Persistence Problems: Ensure Docker Compose files are properly maintained
Development
Conductor includes development tools for code quality and testing:
# Code quality checks
yarn lint
yarn type-check
# Testing
yarn test
# Documentation
yarn docs
Release Notes
0.6.9
Released: February 20, 2026
-
Added DNS configuration for Conductor in
docker-compose.yml, including autoheal support. -
Added retry mechanism for container actions (add, remove, update agents and modules).
-
Changed "Restart Gluesync Instance" (Danger Zone) to perform a full stop and restart using
docker compose downfollowed bydocker compose up.
0.6.8
Released: February 18, 2026
-
Updated logs uploader for Windows that now also includes docker stats
-
Updated docker client for more resilient reconnection in case of sock busy (particularly during cold starts of the Docker Engine on Windows)
0.6.7
Released: February 16, 2026
-
Updated logs uploader for Windows new version with locked file check improvement;
0.6.6
Released: February 12, 2026
-
Adoption of third-party services (Grafana, Prometheus, Traefik, Portainer) also if these are under the latest tag;
-
Fixed an issue that could cause conductor to return a mandatory update tag even if the module was up to date already;
0.6.5
Released: February 11, 2026
-
Updated logs uploader for Windows and linux to new version with FTP improvement;
0.6.4
Released: February 9, 2026
-
Updated collect logs script to improve diagnostics and reliability;
-
Stabilized Windows conductor update process and fixed issues that could prevent proper module updates;
-
Improved stability in service listing and latest-version retrieval within the Modules Manager menu;
-
Enhanced logic for retrieving the latest available module versions;
-
Fixed an issue affecting updates of third-party services.
0.6.3
Released: February 6, 2026
-
Fixed an issue with FTP upload for Windows (file name encoding issue);
0.6.2
Released: February 5, 2026
-
Fixed an issue that could cause the module to fail to update itself;
0.6.0
Released: January 28, 2026
-
Automatically removed
container_nameanddepends_onentries from Docker Compose configurations to improve portability and reduce conflicts. -
Added explicit network configuration for Linux services to prevent rare cases where the SDK failed to reconnect.
-
Introduced TIMEZONE handling via
.env, propagating the value into both core-hub and agents configurations. -
Updated
agents.jsonso Whisperer is correctly recognized and auto-adopted in Gluesync deployments. -
Adopted third-party services (Grafana, Prometheus, Traefik, Portainer) into the deployment stack, allowing full control over version selection.
-
Fixed Dockerfile
ARGhandling to avoid build-time breakages and ensure proper support for the Docker helper image used during conductor restarts.
0.5.8
Released: January 21, 2026
-
Fixed service version detection by resolving running containers via Docker Compose labels instead of relying on container names.
0.5.5
Released: January 5, 2026
-
Added support for restarting all services in containers when no IDs are specified.
0.5.4
Released: December 31, 2025
-
Added agentId in list containers api response;
-
Fixed TAG env for agent nicknaming;
-
Removed container_name from docker compose file to avoid conflicts during updates;
-
Fixed service_id in docker compose file to use the container id instead of the agent id;
-
Fixed auto adopt removing the INITIAL_AGENT_ID handling;
-
Fixed empty object in docker compose file for deploy parameter;
-
Fixed create volume folder with container id instead of container_name;
-
Other minor fixes and improvements;
0.5.1
Released: December 23, 2025
-
Added support for Windows containers on Windows Server 2019
-
Fixed network in some Windows instances
0.4.3
Released: December 16, 2025
-
Pruned images that have no running containers after an update;
-
Preserved architecture-specific suffixes in images during updates;
-
During its update, Conductor does not process requests and responds with a message and HTTP status code 503;
-
Updated the Node.js SDK to connect more fluently to Core Hub after the first connection;
-
Added support for specifying either a full URL or just a hostname in the
GLUESYNC_HOSTenvironment variable;
0.4.1
Released: December 13, 2025
-
Fixed dependency issue for bootstrap-core-hub.json file under agents' management;
0.4.0
Released: November 24, 2025
-
Auto adopt previously hand held services;
-
Removed depends_on in adopted services (even "adopted by hand");
-
Handled update of Conductor by doContainersAction update api;
-
Auto heal Conductor conf if some configuration of Conductor is wrong it will self heal (for now only logs file);
-
If Auto healed auto update Conductor version, no more latest in docker-file;
-
Edited get version api to notify when modules have mandatory updates to be applied.
0.3.1
Released: November 14, 2025
-
Handled read of docker file configuration both in List Style and Map Style;
-
Handled updates only for services handled by Conductor;
0.3.0
Released: November 12, 2025
-
Update with an empty array update all must accept the releaseChannel parameter;
-
With update all: update only containers with core-hub, agent, and module (no conductor);
-
List all containers except third party containers (grafana, prometheus, portainer, or traefik);
-
Fix current version in get latest;
-
Handled null version tag in get latest (which does not fires an actual update);
0.2.1
Released: November 10, 2025
-
Updated Node.js SDK to the latest version;
-
Re-send license headers at every reconnection to the Core Hub;
-
Filter out containers without Id.