While I can fully get on board with the lightweight workloads that containerized services provide, I've always had a problem with the management tools on offer for Windows users. Docker Desktop is a bloated mess, and most of the dashboards I've used to make sense of what's going on in my home lab have more features than I want to learn. I don't need more than the Docker engine running, so I can use Docker Compose in my Terminal, and a way to see which containers I have on the go.

And that's it. I don't need to be able to pull images from a central hub, or to edit files because I can do that nicely in VS Code. I don't want to reinvent the wheel every time I want to type docker compose up -d on the command line, or have to search for where the compose files are saved, or any of the annoyances that make me wish that I hadn't tried running Docker on Windows again. The good thing about containers is that there are a hundred ways to do any task, and I've found a dashboard that shows me what's running, which ports they're using, and links to the image being used, and that's all I need.

What is Dockpeek?

I never realized how much I wanted a lightweight way to manage my containers

I've used many Docker management tools, from Komodo to Portainer, and they all feel like I'm juggling a chain of recursive containers. I already know where my compose files are; I've got them open in VS Code to make changes. I know where my mapped storage folders are, because I can see them in File Explorer. I can monitor memory and CPU usage easily because I'm on the same machine, and having these replicated on my dashboard bugs me.

I've come to the realization that I'm probably atypical in this regards, because every management tool behaves like this. They all stack menus upon menus to to show which containers are running, where your images are, and any little piece of information about your containers that the developer thinks you might want to see. Then you get resource usage and other information on the container name, and it all starts to feel like I'm adding notes in the margins of a book.

I can't work like this. It's the same overwhelm of information that makes Google Analytics or any other monitoring tool impossible for my brain to handle until I've added filters, restrictions, and other ways of pruning down the data so that I have just enough to get me by. And that's what Dockpeek does for me. It shows my containers, the ports I can access them from, if they're running or not, and if they need an updated image.

It's easy to see logs and what's going on

Oh, and logs. The crucial thing, that on most Docker dashboards, I need to click through several layers of tabs to get to. These logs are in a readable, large font, and I can get to them with a single click. I don't want to learn a multi-stage navigation for every container to figure out how to get to the logs and then get from those logs to somewhere I can fix the errors. I just want logs.

Why is Dockpeek better for me?

Exhibit A: Docker Desktop and its bloat

I'm calling out Docker Desktop specifically, but Podman is just as bad. Even with my glasses on, I can't read half of the text on the interface, and the logging section is even worse. If I can't read it, why are you insisting that you show it to me?

I know I sound like an old man shouting at the sky, but these tools are supposed to make container management easier, not add another stack of cognitive load that I need to work through and squint at to see. The closest to a usable dashboard I've used is Dockge, which, at the very least, keeps the font size large. But again, it duplicates functionality that I have elsewhere and that I'm already comfortable working in.

Why do I need all of these other things?

I prefer to start any containerized task with a compose file, and I tend to do the rest of the process manually as well. I don't like context-switching between text-based management and buttons, and I've always had an issue with systems like Synology Container Manager, where everything is done in forms to be filled out. I don't need to be able to search through a registry of existing Docker images, because I'm usually working directly from the directions on the Github page. My workflow just doesn't need the layers of functionality that most Docker dashboards provide, and I'm okay with that. I know what works for my brain and any time I have to work against that, I end up spending more time fighting with my tools and workflow than actually doing the thing I set out to accomplish.

Dockpeek has made container management make sense to me

When I'm handling Docker containers to build out home lab experiments, I'm a man of simple needs. I need a Terminal, a text editor, and a dashboard that can show me which pieces of my stack are running, and any logs that I'll need to figure out why something isn't working as intended. I don't want to replicate any of these features inside my dashboard, I don't even want to have buttons to restart my containers, because I'd rather use the command line.

Dockpeek gives me just enough information to know what's going on while I'm working, without having the cognitive load associated with navigating a cluttered interface. And that's all I want, a visual reminder of what's working, and a button to pull the latest version of each container.