Dockpeek - All Your Docker Containers at a Glance

Sound familiar: a dozen containers are running, web interfaces scattered across different ports, and IP addresses jumbled in your head. Dockpeek solves this problem with one elegant move — providing a clean dashboard with all active containers and their ports, accessible in literally one click.

What is this tool?

Dockpeek is a lightweight, self-contained web interface for Docker. Unlike heavyweight solutions like Portainer, it focuses on a single task: quick access to running services. The project is written in Python using FastAPI and works great even on low-end machines.

Who is this for?

Developers testing multiple microservices
System administrators managing several Docker hosts
Home lab enthusiasts with a bunch of self-hosted services

5 reasons to try Dockpeek right now

Instant access to services No more memorizing or searching for ports — just click on the service you need in the web interface. Dockpeek automatically detects HTTP/HTTPS and constructs the correct link.
Multi-host support Connect multiple Docker hosts (local and remote) in a single interface. Especially convenient when you have separate servers for development, testing, and production.

Image update tracking Built-in update checking shows which of your containers are running outdated image versions — no more surprises with vulnerabilities.
Port search Need to quickly find who's using port 8080? Just enter :8080 in the search bar.
Zero configuration Docker socket mounts automatically, all running containers are detected without additional setup.

How it works under the hood

Dockpeek communicates with Docker through the standard API, using:

Local Unix socket for Docker Engine access
Or TCP connection for remote hosts (recommended via socket-proxy for security)

The architecture is straightforward:

Frontend (Vue.js) ↔ Backend (FastAPI) ↔ Docker API

Practical use cases

For developers

Imagine: you're working on a microservice architecture with a dozen components. Each runs in a separate container on different ports. Instead of keeping all those localhost:32768 in your head (or in notes), you get a unified interface with clickable links.

For system administrators

When managing a cluster of multiple Docker servers (e.g., main server + backup + test), Dockpeek becomes a single entry point for monitoring all containers.

For home use

If you have a home lab set up with services like:

Plex/Jellyfin for media
Nextcloud for files
Home Assistant for smart home Dockpeek will turn your browser into a convenient control panel.

Getting started

Local run via Docker Compose:

services:
  dockpeek:
    image: ghcr.io/dockpeek/dockpeek:latest
    container_name: dockpeek
    environment:
      - SECRET_KEY=my_secret_key
      - USERNAME=admin
      - PASSWORD=admin
    ports:
      - "3420:8000"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    restart: unless-stopped

After startup, the interface will be available at http://localhost:3420.

Conclusion: is it worth trying?

Dockpeek is not a replacement for full-featured management panels like Portainer, but a convenient addition to them. If you need to:

Quickly access container web interfaces
Monitor image updates
Have a simple overview of all running services

...then this tool will save you a lot of time. Especially recommended for developers working with multiple microservices simultaneously — after Dockpeek, going back to manual port entry is something you won't want to do.