Logs, stats, and control for all your containers

LogDeck is an open-source dashboard and CLI for Docker and Podman. Stream logs, watch resource usage, and manage containers across every host you run.

Try the demo Install

Star on GitHub

LogDeck dashboard showing containers across hosts with live CPU and memory sparklines, compose stack groups, and quick actions

Everything you need to run containers

One binary with the frontend embedded. No database, no agents on your hosts.

Live log streaming: Follow logs in real time with pause, auto-scroll, and timestamps. Thousands of lines stay smooth.
Search and filtering: Full-text search with match navigation, log level filters, and calendar-based time ranges.
Multi-host: Manage local, TCP, and SSH daemons from one dashboard. Every container, one list.
Docker and Podman: Works with both engines, rootless or rootful, side by side in the same setup.
Compose stacks: Start, stop, or restart whole stacks, and read stack logs merged by timestamp.
Stats and trends: Live CPU and memory per container, with sparklines covering the last five minutes.
Resource limits: Change memory limits, CPU limits, and restart policies live — no recreate, no downtime.
Command-line client: A scriptable logdeck CLI with JSON output, built for automation and AI agents.
Web terminal: Open a shell in any running container straight from the browser.
Images, volumes, networks: Read-only views of everything else on your hosts, aggregated and filterable.
Environment variables: View and edit container env vars, with bulk paste from .env files.
Auth and API tokens: Optional login, API tokens for external tools, and a read-only mode for production.

Built around the log view

Streaming logs with search, level filters, time ranges, and one-click download — for a single container or a whole Compose stack merged by timestamp.

LogDeck log viewer with search, level filters, and streaming logs

Also a command-line client

The logdeck CLI talks to the same API as the web UI. Search logs across every container, follow a service, or restart a stack — with JSON output for scripts and AI agents.

Read the CLI guide

# search the last hour of logs across every container
logdeck grep "connection refused" --since 1h

# follow one service, errors only
logdeck logs api --follow --level ERROR

# act, then confirm
logdeck restart redis --host prod
logdeck stats redis

Install

One container for the server, one command for the CLI. No database, nothing to migrate.

Read the docs

services:
  logdeck:
    image: amoabakelvin/logdeck:latest
    container_name: logdeck
    ports:
      - "8123:8080"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /proc:/host/proc:ro
    environment:
      # Optional: manage multiple hosts
      # DOCKER_HOSTS: local=unix:///var/run/docker.sock,prod=ssh://deploy@prod.example.com
      # Optional: enable authentication
      # JWT_SECRET: your-super-secret-key-min-32-chars
      # ADMIN_USERNAME: admin
      # ADMIN_PASSWORD_SALT: your-random-salt-change-this
      # ADMIN_PASSWORD: your-sha256-hash
    restart: unless-stopped

docker compose up -d

Then open http://localhost:8123. Your containers are already there.