dry mit Homebrew, Nix installieren

Projektlinks

• Homepage
• Repository

Befehle und Aliase

• dry

Projektgeschichte

The project emerged during the Docker Swarm era as an alternative interface to repeated `docker` CLI invocations. Its README emphasizes parity with many official Docker CLI commands, local or remote Docker daemon support, monitoring use cases, and single-binary installation.

Adoptionsgeschichte

dry's adoption is mostly among terminal-first Docker users who want an interactive dashboard without a web console. Official badges and docs point to GitHub releases and Snap packaging, while Homebrew and Nix packaging make it easy to install on developer workstations.

Wie es verwendet wird

Users run `dry` to browse Docker resources, inspect selected objects, tail logs, execute into containers, view daemon events, and manage Swarm constructs. Its keyboard-driven interface makes it a lightweight local operations tool rather than a cluster control plane.

Warum Paket-Nerds sich dafür interessieren

dry is package-nerd interesting because it is a Go-era single binary that wraps a large external platform without bundling that platform. The package is small, but its usefulness depends entirely on a reachable Docker daemon and on staying compatible with Docker's API behavior.

Zeitleiste

• 2010s: dry appears as a terminal application for Docker and Docker Swarm management.
• Later: The README documents single-binary installation and command/keybinding coverage for containers, images, networks, volumes, and Swarm resources.
• Packaging era: The project advertises GitHub release workflows and package surfaces such as Snap, Homebrew, and Nix.

Related projects

• Docker and Docker Swarm are the managed platforms.
• The official Docker CLI is the behavior reference for many dry commands.
• Snap, Homebrew, and Nix are common package-distribution neighbors for the single binary.

Quellen

• https://github.com/moncho/dry
• https://github.com/moncho/dry/blob/master/README.md
• https://moncho.github.io/dry