Automatically registers and deregisters Docker containers as services in pluggable service registries like Consul, etcd, and SkyDNS.
Registrator is a service registry bridge for Docker that automatically registers and deregisters containers as services in pluggable service registries like Consul, etcd, and SkyDNS. It solves the problem of manual service discovery configuration in dynamic container environments by inspecting containers as they start and stop.
DevOps engineers and developers building microservices architectures with Docker who need automated service discovery and registration without manual intervention.
Developers choose Registrator for its simplicity, automatic container lifecycle management, and support for multiple popular service registries through a pluggable adapter system, reducing operational overhead in containerized deployments.
Service registry bridge for Docker with pluggable adapters
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Inspects Docker containers as they start and stop, automatically registering and deregistering services with configurable policies like 'always' or 'on-success' for cleanup.
Supports multiple service registries including Consul, etcd, and SkyDNS 2 through a pluggable architecture, allowing flexibility in backend choice without code changes.
Offers CLI options for IP binding, internal vs published ports, service tags, TTL management, and cleanup of dangling services, as detailed in the usage section.
Includes resynchronization and TTL refresh features to periodically sync services with the registry, maintaining consistency in dynamic environments.
Only supports Consul, etcd, and SkyDNS 2, lacking adapters for newer or alternative service discovery systems like Eureka or HashiCorp's Nomad, which may limit adoption in diverse stacks.
Requires mounting the Docker socket (/var/run/docker.sock), which can expose the host to security risks if not properly secured, making it less ideal for locked-down production environments.
Does not inherently integrate advanced health checking for services; relies on the backend registry for health status, which might require additional tooling for robust monitoring.
As a project from gliderlabs, it may receive fewer updates compared to more actively maintained alternatives, possibly missing features from modern container orchestration trends.