Skip to content

Power Variant

~91 MB: Full SRE-grade forensics toolkit.

Everything from balanced, plus advanced tools for deep system and network investigation.

When to Use Power

  • Detailed packet analysis with tshark
  • Port scanning and service discovery with nmap
  • Network performance testing with iperf3
  • Library-level tracing (ltrace)
  • Advanced routing and firewall debugging
  • Deep incident forensics
  • Not recommended for routine tasks. Stick with balanced to save bandwidth

Linux Capabilities Required

Power variant tools like tshark, conntrack, iptables, and nftables require additional Linux capabilities to function.

→ Kubernetes capability setup → Docker capability setup

Quick Usage

kubectl debug my-pod -it --image=ghcr.io/ibtisam-iq/debugbox:power

For tools that require capabilities (tshark, conntrack, iptables), use a manifest:

kubectl apply -f \
  https://raw.githubusercontent.com/ibtisam-iq/debugbox/main/examples/power-debug-pod.yaml
kubectl wait pod/debug-power --for=condition=Ready --timeout=60s
kubectl exec -it debug-power -- bash -l

→ All tag formats | Kubernetes usage | Docker usage

What's Included

Power includes all balanced tools plus advanced forensics packages for packet analysis, network scanning, and routing inspection.

→ Complete tool list | Usage examples

Key additions over balanced:

  • Packet Analysis: tshark, ngrep (requires NET_RAW)
  • Network Scanning: nmap, nmap-nping, nmap-scripts
  • Network Performance: iperf3, ethtool, iftop
  • Routing & Firewall: iptables, nftables, conntrack (requires NET_ADMIN)
  • Advanced Network: tcptraceroute, fping
  • System Internals: ltrace

Shell Helpers

Power includes all balanced helpers plus 1 additional helper:

→ Complete shell helper reference with examples

Power-exclusive helper:

  • conntrack-watch(): List active conntrack entries (requires NET_ADMIN)

When to Downgrade

Most tasks use Balanced Variant. Downgrade to save ~44 MB.

For speed, use Lite Variant. Saves ~76 MB.

→ Variants Overview | Real-world Examples | Troubleshooting