nicolaka/netshoot

a Docker + Kubernetes network trouble-shooting swiss-army container

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 5th, 2026
Created on August 24th, 2016
Open Issues & Pull Requests: 43 (+0)
GitHub issues: Enabled
Number of forks: 1,099
Total Stargazers: 10,979 (+0)
Total Subscribers: 127 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 83.9 days
Mean response time: 161.2 days
90th percentile: 258.6 days
Tracked items: 13

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 651 days
Stale 30+ days: 9
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

netshoot is a Docker and Kubernetes network troubleshooting container that bundles diagnostic tools into a single image.

The tool solves the problem of diagnosing network issues in containerized environments where standard networking utilities may not be available in production images. Rather than installing tools into application containers or maintaining separate debugging images, netshoot provides a pre-built container with a comprehensive set of network diagnostic utilities. Users can deploy it as a sidecar, run it alongside problematic containers, or execute it within Kubernetes clusters to inspect network behavior, connectivity, and configuration without modifying production workloads.

Teams managing Docker or Kubernetes infrastructure should adopt netshoot when they need quick access to network debugging capabilities in containerized environments. It suits projects where network troubleshooting is frequent enough to justify a dedicated tool but not so specialized that custom debugging containers are warranted. The approach works well for developers and operators who want to avoid the overhead of building custom diagnostic images or the risk of adding debugging tools to production containers.

Development activity shows consistent maintenance with regular updates to keep the bundled tools current. The project accepts contributions from the community and incorporates feedback through pull requests. Documentation is actively maintained to reflect the container's capabilities and usage patterns. The tool receives ongoing attention to ensure compatibility with evolving Docker and Kubernetes versions.