Getting Started
Welcome to LogDeck! Get started in minutes with our Docker-based deployment.
What is LogDeck?
LogDeck is an open-source tool designed to be the most intuitive and visually appealing solution for monitoring Docker container logs and managing containers. Built with modern web technologies and a Go backend, LogDeck provides a beautiful interface for working with Docker.
Why LogDeck?
Docker's command-line tools are powerful but can be cumbersome for everyday use. LogDeck provides:
- Real-time log streaming - Watch your container logs update in real-time with automatic scrolling
- Multi-host management - Connect to multiple Docker daemons (local, TCP, or SSH) and manage them from one UI
- Advanced filtering - Search, filter by log level, and use regex to find exactly what you need
- Container management - Start, stop, restart, and remove containers with a single click
- Beautiful UI - A modern, responsive interface that works on desktop and mobile
- Zero configuration - Works out of the box with sensible defaults
- Optional authentication - Secure your instance or run it completely open
Quick Start
The fastest way to get LogDeck running is with Docker Compose:
version: '3.8'
services:
logdeck:
image: logdeck/logdeck:latest
container_name: logdeck
ports:
- "8123:8123"
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
restart: unless-stoppedSave this as docker-compose.yml and run:
docker-compose up -dThen open your browser to http://localhost:8123
What's Next?
Now that you have LogDeck running, here are some next steps:
- Installation Guide - Learn about different deployment options
- Features - Discover all the features LogDeck offers
- Configuration - Configure authentication, environment variables, and more
System Requirements
- Docker Engine 20.10 or later
- Access to the Docker socket (
/var/run/docker.sock) - Modern web browser (Chrome, Firefox, Safari, or Edge)
- Network access and credentials for any remote Docker hosts if using multi-host mode
Getting Help
If you encounter any issues or have questions:
- Check the GitHub Issues for known problems and solutions
- Open a new issue on GitHub