# cdebug mit Homebrew, MacPorts installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für cdebug in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:cdebug
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install cdebug
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install cdebug
```

  Evidenz: MacPorts ports tree: sysutils/cdebug/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:cdebug
- **Paketmanager:** Homebrew
- **Version:** 0.0.19
- **Quellzusammenfassung:** Swiss army knife of container debugging
- **Homepage:** <https://iximiuz.com/en/posts/docker-debug-slim-containers/>
- **Repository:** <https://github.com/iximiuz/cdebug>
- **Zuletzt aktualisiert:** 2026-07-27T19:20:57+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- cdebug (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.0.19
## Projektgeschichte und Nutzung

cdebug is a Go-based command-line tool for debugging containers and Kubernetes pods, especially slim, scratch, and distroless images that do not include a shell or troubleshooting tools.

### Projektgeschichte

The upstream README calls cdebug a 'swiss army knife of container debugging' and documents commands for exec-style debugging, local port forwarding, and exporting or inspecting container filesystems. Its exec workflow is explicitly based on ideas from the iximiuz article about debugging slim Docker containers.

The GitHub releases begin with v0.0.1 on 2022-11-06 and continue through v0.0.19 on 2026-01-18, showing an active small-tool release history around container debugging workflows.

### Adoptionsgeschichte

cdebug entered package-manager culture as a modern container-debugging utility rather than a classic Unix tool. The Homebrew input records Homebrew and MacPorts packaging, and the upstream README documents Homebrew installation for macOS and Linux.

### Wie es verwendet wird

Users run cdebug exec against Docker, containerd, nerdctl, or Kubernetes targets to start a temporary debugging sidecar whose tools are available in the target container's filesystem view. The README also documents cdebug port-forward for exposing unpublished or localhost-only container ports.

### Warum Paket-Nerds sich dafür interessieren

cdebug is notable because it packages a container namespace trick into a single statically linked binary. It sits in the practical space between docker exec, kubectl debug, nsenter-style debugging, and ad hoc sidecar containers, which makes it attractive to operators dealing with minimal images.

### Zeitleiste

- 2022-11-06: v0.0.1 and v0.0.2 published.
- 2022-12: v0.0.4 through v0.0.6 published.
- 2023: Multiple releases through v0.0.14.
- 2024: v0.0.15 through v0.0.18 published.
- 2026-01-18: v0.0.19 published.

### Related projects

- The upstream README frames cdebug exec as a cross between docker exec and kubectl debug, and points to Nixery as a way to build custom debugging images.

### Quellen

- <https://api.github.com/repos/iximiuz/cdebug>
- <https://github.com/iximiuz/cdebug>
- <https://iximiuz.com/en/posts/docker-debug-slim-containers/>
- <https://github.com/iximiuz/cdebug#readme>
- <https://formulae.brew.sh/api/formula/cdebug.json>
- <https://github.com/iximiuz/cdebug/releases>
- <https://iximiuz.com/en/posts/docker-debug-slim-containers>


## Sicherheitshinweise

infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- infrastructure mutation or orchestration signal

## Andere Paketmanager-Einträge

- MacPorts - cdebug: normalized package name match | MacPorts ports tree: sysutils/cdebug/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1


## Combined YAML source

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


## Quellen

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