Skip to content

1.1.0 — Compose support and topology dashboard

Choose a tag to compare

@LimeBeck LimeBeck released this 15 Sep 19:45
· 8 commits to master since this release
7f9161b

Compose support

The existing dev.limebeck.libs:docker-client artifact now includes dev.limebeck.libs.docker.compose on JVM, NodeJS and Linux X64.

  • Discover existing Compose projects/services from Docker labels, including replicas, stopped containers and one-offs.
  • Read project-wide or selected-service logs with container identity, a single-service overload, bounded subscriptions and cancellation cleanup.
  • Reuse the owning DockerClient endpoint and lifetime; no new runtime dependency or installed Compose CLI is required for these APIs.

Dashboard

  • Host overview with observed container counts, attention list, Compose summaries and live events.
  • Engine version, OS, architecture, memory and CPU loaded once in the sidebar.
  • Compose services, containers, volumes, networks and logs views.
  • Network topology with container cards, host port bindings and an inspector for state, health, logs, configuration and latest memory statistics.
  • Bundled service icons, responsive layout and separate port/mount sections.

Compatibility

This is an additive minor release. Existing Engine APIs remain available. Supported targets remain Linux JVM 17+, Kotlin/JS on Node.js and Linux X64 Native, using fixed Docker API 1.51.

Compose support reflects existing Engine resources. It does not parse YAML, infer dependency/traffic graphs, or implement Compose up/down/start/stop orchestration. Historical health may remain on stopped containers. Topology distinguishes configured bindings from currently published ports.

Maven coordinates: dev.limebeck.libs:docker-client:1.1.0.

Compose guide · Dashboard guide · API reference

Dashboard executable

Download the attached Linux X64 htmxDashboard.kexe, then run:

chmod +x htmxDashboard.kexe
./htmxDashboard.kexe /var/run/docker.sock 18081

Open http://127.0.0.1:18081. This remains a local development dashboard.

Passed PR matrix · Release CI

Maven Central publication was accepted successfully by Release CI. Public repository propagation is still in progress; dependency resolution may temporarily return 404.