# Install docker-debug with Homebrew

Use new container attach on already container go on debug. Version 0.7.11 via Homebrew; verified 2026-07-28.

## Install

```sh
sudo av install brew:docker-debug
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install docker-debug
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:docker-debug
- **Package manager:** Homebrew
- **Version:** 0.7.11
- **Source summary:** Use new container attach on already container go on debug
- **Homepage:** <https://github.com/zeromake/docker-debug>
- **Repository:** <https://github.com/zeromake/docker-debug>
- **Last updated:** 2026-07-28T14:10:40+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- docker-debug (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.7.11
## Project history and usage

docker-debug is a small troubleshooting CLI that starts a new debug container joined to a running target container's namespaces, allowing tools to be supplied from a separate image instead of being baked into the production image.

### Project history

The README presents docker-debug as inspired by kubectl-debug and aimed at inspecting running Docker containers by joining PID, network, user, filesystem, and IPC namespaces. It uses nicolaka/netshoot as the default debug image and supports overriding behavior with flags or a local TOML config file.

The changelog shows rapid development in 2019 around mounting filesystems and volumes, adding a Homebrew install path, default config from environment, and config version management. Later entries are sparse, with v0.7.4 in 2022 documenting Docker client-version work and volume path handling.

### Adoption history

Evidence for broad adoption is thin. The project documents Homebrew and binary-release installation, but the upstream materials mostly frame it as a focused utility for users who want Kubernetes-style ephemeral debugging against plain Docker containers.

### How it is used

A typical invocation is docker-debug CONTAINER COMMAND. The tool creates a separate debug container, joins the target container's namespaces, mounts the target filesystem, runs the requested command, and then cleans up after the debug container exits.

### Why package nerds care

docker-debug is interesting to package nerds because it packages an operations pattern rather than a large platform: ship debug tools separately, keep runtime images small, and use Linux namespaces to inspect a live workload. Its niche also makes it a good example of the long tail of Docker-era helper CLIs in Homebrew.

### Timeline

- 2019: early v0.2.x-v0.6.x changelog entries add Homebrew installation, mounted filesystems, volume filesystem support, and config defaults.
- 2020: v0.7.x releases include config client-version and migration fixes.
- 2022: v0.7.4 documents Docker client-version work and volume path support.

### Related projects

- The README names kubectl-debug as the inspiration, nicolaka/netshoot as the default debug image, and Docker Engine API documentation as a reference.

### Sources

- <https://github.com/zeromake/docker-debug#readme>
- <https://github.com/zeromake/docker-debug/blob/master/CHANGELOG.md>
- <https://github.com/zeromake/docker-debug/releases>


## Security Notes

infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- infrastructure mutation or orchestration signal


## Combined YAML source

View the package source record on GitHub. [combined/docker-debug.yml](https://github.com/mxcl/pkgdb/blob/main/combined/docker-debug.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph