yeet-src/container-explorer — explained in plain English
Analysis updated 2026-05-18
Watch live CPU, memory and network usage for a specific running container.
See the real processes running inside a container without separate inspect commands.
Debug a crashing container by viewing its status, restart count and logs on one screen.
Review a container's networks, ports and mounted volumes in a single view.
| yeet-src/container-explorer | botpress/solutions | mourner/icomesh | |
|---|---|---|---|
| Stars | 68 | 68 | 68 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | — | 2024-09-03 | 2019-09-27 |
| Maintenance | — | Stale | Dormant |
| Setup difficulty | easy | moderate | easy |
| Complexity | 2/5 | 2/5 | 2/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Linux only, and Docker must already be running and reachable on the machine.
Container Explorer is a terminal tool for anyone who manages Docker containers and is tired of switching between separate commands to check what is running, how much memory something is using, and what its logs say. Normally you would run one command to list containers, another to see their stats, and another to tail their logs, then piece the results together in your head. This tool puts all of that into a single, constantly updating screen instead. Open it and you see a live table of every container running on the machine, showing its name, image, how long it has been up, and its current status. Selecting a container and pressing enter opens a detailed view with several sections: live charts of CPU, memory and network use, the container's attached networks and ports, its file mounts, the actual processes running inside it, and a log tail that follows new output as it happens. Because it matches host processes to the right container directly, you see the real running processes instead of a guess. To be efficient about it, only the container you currently have open on screen gets closely polled for detailed information. The rest of the containers in the list are refreshed with a much lighter, cheaper check every couple of seconds, so having many containers running does not slow things down or hammer the Docker daemon. Common situations this helps with include figuring out which container is using too much CPU or memory, checking what is actually running inside a container during a crash, and reviewing a container's network setup without running several separate inspect commands. Getting started is a single install command followed by one command to run the tool, and it works entirely with the keyboard and mouse with no configuration flags to learn. It currently only works on Linux and requires Docker to already be running on the machine. It is released under the GPL-2.0 license.
Container Explorer is a terminal tool that shows a live, drill-down view of every running Docker container, its stats, processes, and logs in one screen.
Mainly JavaScript. The stack also includes JavaScript, Docker, GraphQL.
You can use and modify this freely, but if you distribute it or a modified version, you must also share the source code under the same license.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.