Inspektor Gadget
Inspektor Gadget is a command-line toolkit that uses eBPF (extended Berkeley Packet Filter) to trace and observe activity inside Linux hosts and containers.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
75/100 Good
- Maintained
- 100last commit 16 days ago
- Popular
- 692,959 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 81no serious findings, 3 minor, CI, tests, OpenSSF Scorecard 8/10
Based on 4 of 5 factors.
- GitHub stars
- 2,959
- Open issues
- 425
- Last commit
- 2026-11-05
- Latest release
- v0.58.0
- License
- Apache-2.0
- Activity
- declining
Checked 16 days ago - source: GitHub (inspektor-gadget/inspektor-gadget)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Test hooks with a tiny busybox pod Use `kubectl run -ti --rm --image busybox shell1 -- sh` to start a short-lived busybox (a tiny container image) pod. If you skip this, container-hook examples have no pod to watch, so they may show no start or stop events. source
- Use sudo and --host to trace Docker For the fdpass (file-descriptor passing) example, run the gadget with `sudo` and `--host` while starting a Docker container. Without those, the gadget may not see the host-level setup Docker performs when a container starts. source
- Point remote ig daemon to the right host If you use the `ig` daemon on another machine, replace the example IP and PORT with your actual address and include the gadget public keys (small files used to check gadget signatures). Without the correct address and keys, remote gadget clients cannot verify or run gadgets. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Why do the container-hook examples show no container start or stop events?
You need to start a short-lived busybox pod so the examples have a pod to watch. If you skip it, the examples have nothing to monitor and may show no events.
Why might the fdpass example miss Docker container startup details?
Run the gadget with sudo and --host while starting the Docker container. Without those flags, it may not see the host-level setup Docker performs when a container starts.
How do I point a remote Inspektor Gadget client at the ig daemon?
Use the daemon's actual IP address and port. You also need the gadget public keys used to verify signatures, or the remote client cannot verify or run gadgets.
Can I run Inspektor Gadget for a one-off check instead of keeping it installed?
It supports both ephemeral commands and permanent installation. You can use it for short-lived inspection or install it for ongoing use.
Answers sourced from github.com, github.com, github.com, inspektor-gadget.io
Community
- Inspektor gadget deep dive : r/kubernetes - Reddit (reddit)
- Inspector Gadget - Reddit (reddit)
- inspector gadget - Reddit (reddit)
Collected 48 days ago - public community threads