jpetazzo/nsenter
None observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4458
- days_rel: n/a
- days_push: 2289
- n_releases_24m: 0
Adoption not part of the score
2581 stars · 268 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A small Docker recipe that builds the nsenter utility and installs it on the host, letting users enter Linux namespaces of running Docker containers. It was created when distros shipped outdated util-linux versions lacking nsenter, and is now obsolete and unmaintained.
Use cases
- enter a running docker container's namespaces
- install nsenter binary on old distros without util-linux 2.23
- debug a container from outside its cgroups
- audit a container process externally
- spawn a process into a container's namespaces
When to choose
- you are on a very old distro without nsenter in util-linux
- you need to enter container namespaces without joining its cgroups for debugging
When to avoid
- you just want a shell in a container — use docker exec instead
- you run any modern distro that already ships nsenter
- you need maintained, supported tooling
Facets
cli-tool · maturity abandoned
cli container-runtime developer-tools developer-tools cli docker namespaces nsenter container-debugging shell-script containers devops linux
1 source
- readme: https://github.com/jpetazzo/nsenter · fetched 2026-08-28 · 96cf61325840
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| jpetazzo/nsenter | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="jpetazzo/nsenter")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem