Automic VaultAutomic Vault

brew

Install docker-debug with Homebrew

Use new container attach on already container go on debug. Version 0.7.11 via Homebrew; verified from local package data.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrewverified · 100%
brew install docker-debug

local Homebrew formula metadata

overview

Package summary

Use new container attach on already container go on debug

Commands and aliases

  • docker-debug

history

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.

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • infrastructure mutation or orchestration signal

Signals

  • text:container

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
docker-debugcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version0.7.11
manager updated
local dataok
upstreamcurrent
latest detectedv0.7.11

https://github.com/zeromake/docker-debug

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:docker-debug
Version0.7.11
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/docker-debug
Homepagehttps://github.com/zeromake/docker-debug
Repositoryhttps://github.com/zeromake/docker-debug
Upstream docshttps://github.com/zeromake/docker-debug#readme
LicenseMIT
Source archivehttps://github.com/zeromake/docker-debug/archive/refs/tags/v0.7.11.tar.gz
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namedocker-debug
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

Related tools

  • goBuild dependency declared by Homebrew.
  • docker-genPackage names and metadata indicate a similar tool family. Shared terms: cli, container, containers, developer, developer-tools.

Same workflow

  • cdebugShares av.db curated category or tags: cli, containers, debugging, developer-tools, docker.
  • gebugShares av.db curated category or tags: cli, containers, debugging, developer-tools, docker.
  • cekitShares av.db curated category or tags: cli, containers, developer-tools, docker.
  • devcontainerShares av.db curated category or tags: cli, containers, developer-tools, docker.
  • dockcheckShares av.db curated category or tags: cli, containers, developer-tools, docker.
  • dockerShares av.db curated category or tags: cli, containers, developer-tools, docker.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment