gliderlabs/docker-consul resource
Dockerized Consul observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4481
- days_rel: n/a
- days_push: 1989
- n_releases_24m: 0
Adoption not part of the score
1060 stars · 270 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A Dockerized packaging of HashiCorp Consul, providing Dockerfiles and scripts to run Consul in containers. It was formerly known as progrium/consul, with that version preserved on the legacy branch.
Use cases
- run consul in docker
- dockerized consul service discovery
- set up consul container for local development
- consul kv store in a container
- spin up consul cluster with docker
When to choose
- you need a quick containerized Consul for local development or testing
- you want a minimal Dockerfile base for running Consul
When to avoid
- you need an actively maintained image with recent Consul versions
- you want official support - use the official hashicorp/consul Docker image instead
- you need production-grade updates or security patches
Facets
infra-config · maturity abandoned
container-runtime service-discovery configuration-management developer-tools microservices self-hosted self-hosted consul docker-image dockerfile hashicorp service-mesh kv-store devops containers docker linux
1 source
- readme: https://github.com/gliderlabs/docker-consul · fetched 2026-08-28 · 735842013cbe
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| gliderlabs/docker-consul | main | 32 |
For agents
markdown · JSON · MCP: product_card(name="gliderlabs/docker-consul")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem