docs(gremlin): update dozzle
This commit is contained in:
parent
71086896e2
commit
d35a59f375
1 changed files with 53 additions and 33 deletions
|
|
@ -1,33 +1,50 @@
|
||||||
# dozzle Stack
|
---
|
||||||
|
title: dozzle Stack
|
||||||
|
description: Docker log viewer for NetGrimoire
|
||||||
|
published: true
|
||||||
|
date: 2026-04-30T04:06:05.663Z
|
||||||
|
tags: docker,swarm,dozzle,netgrimoire
|
||||||
|
editor: markdown
|
||||||
|
dateCreated: 2026-04-30T04:06:05.663Z
|
||||||
|
---
|
||||||
|
|
||||||
Overview
|
# dozzle
|
||||||
--------
|
|
||||||
|
|
||||||
The dozzle stack is a Docker Swarm configuration for Dozzle, a tool used to monitor and analyze Docker logs.
|
## Overview
|
||||||
|
The dozzle stack is a Docker Swarm configuration that provides a web-based interface for viewing and managing Docker log data in NetGrimoire.
|
||||||
|
|
||||||
## Architecture
|
## Architecture
|
||||||
| Service | Image | Port | Role |
|
| Service | Image | Port | Role |
|
||||||
|---------|-----|-----|-----|
|
|---------|-------|------|-----|
|
||||||
- **Host:** docker4
|
- **Host:** docker4
|
||||||
- **Network:** netgrimoire
|
- **Network:** netgrimoire
|
||||||
- **Exposed via:** dozzle.netgrimoire.com
|
- **Exposed via:** dozzle.netgrimoire.com, Internal only
|
||||||
- **Homepage group:** Management
|
- **Homepage group:** Management
|
||||||
|
|
||||||
Build & Configuration
|
---
|
||||||
|
|
||||||
|
## Build & Configuration
|
||||||
|
|
||||||
### Prerequisites
|
### Prerequisites
|
||||||
This stack requires a Docker environment with the necessary prerequisites, including a compatible operating system and the Docker client.
|
No specific prerequisites for this stack.
|
||||||
|
|
||||||
### Volume Setup
|
### Volume Setup
|
||||||
```bash
|
```bash
|
||||||
mkdir -p /DockerVol/dozzle
|
mkdir -p /DockerVol/dozzle
|
||||||
chown -R docker:docker /DockerVol/dozzle
|
chown -R docker4:docker4 /DockerVol/dozzle
|
||||||
```
|
```
|
||||||
|
|
||||||
### Environment Variables
|
### Environment Variables
|
||||||
```bash
|
```bash
|
||||||
# generate: openssl rand -hex 32
|
# generate: openssl rand -hex 32
|
||||||
|
CADDY_API_KEY=...
|
||||||
|
CADDY_TLS_CERT=...
|
||||||
|
CADDY_TLS_KEY=...
|
||||||
|
|
||||||
DOZZLE_MODE=swarm
|
DOZZLE_MODE=swarm
|
||||||
|
|
||||||
|
HOME=/var/www/html
|
||||||
|
LOGDIR=/var/log
|
||||||
```
|
```
|
||||||
|
|
||||||
### Deploy
|
### Deploy
|
||||||
|
|
@ -41,47 +58,47 @@ docker stack services dozzle
|
||||||
```
|
```
|
||||||
|
|
||||||
### First Run
|
### First Run
|
||||||
After the initial deployment, you need to update the configuration and restart the service.
|
After the initial deployment, you may need to update the Caddy configuration file (`/etc/caddy/Caddyfile`) to include the DNS record for your domain.
|
||||||
|
|
||||||
User Guide
|
---
|
||||||
|
|
||||||
|
## User Guide
|
||||||
|
|
||||||
### Accessing dozzle
|
### Accessing dozzle
|
||||||
| Service | URL | Purpose |
|
| Service | URL | Purpose |
|
||||||
- **dozzle** | http://dozzle:8080 | Docker log viewer |
|
|---------|-----|---------|
|
||||||
|
- **dozzle**: https://dozzle.netgrimoire.com
|
||||||
|
|
||||||
### Primary Use Cases
|
### Primary Use Cases
|
||||||
To use Dozzle effectively in NetGrimoire, familiarize yourself with its features and configure it according to your needs.
|
To view Docker log data, navigate to the dozzle interface and select the desired container or service.
|
||||||
|
|
||||||
### NetGrimoire Integrations
|
### NetGrimoire Integrations
|
||||||
This service integrates with other services in NetGrimoire, including the reverse proxy and monitoring systems. The DOZZLE_MODE environment variable indicates that this is a Swarm configuration.
|
This stack connects to other services in NetGrimoire via the environment variables `HOME` and `LOGDIR`.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Operations
|
## Operations
|
||||||
|
|
||||||
### Monitoring
|
### Monitoring
|
||||||
$kuma monitors dozzle
|
Check the monitoring dashboard for Uptime Kuma at http://dozzle:8080/monitor.
|
||||||
```bash
|
```bash
|
||||||
docker stack services dozzle
|
docker stack services dozzle
|
||||||
|
docker service logs -f dozzle
|
||||||
```
|
```
|
||||||
The `docker service logs` command can be used to view the logs of the Dozzle container.
|
|
||||||
|
|
||||||
### Backups
|
### Backups
|
||||||
Critical data stored in the /DockerVol/dozzle directory requires careful backup and restore procedures.
|
Critical data should be backed up regularly to prevent loss in case of a failure. The `/var/log` directory on the host machine is used for storing log files.
|
||||||
|
|
||||||
### Restore
|
### Restore
|
||||||
```bash
|
To restore the stack from a backup, you need to delete the existing stack and re-deploy it with the backup configuration file (`dozzle-backup.yml`).
|
||||||
cd services/swarm/stack/dozzle
|
|
||||||
./deploy.sh
|
|
||||||
```
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Common Failures
|
## Common Failures
|
||||||
|
1. **Caddy Not Starting**: Symptoms: Caddy is not responding. Cause: Incorrect Caddy configuration or DNS record issues. Fix: Update the Caddy configuration file and ensure that the DNS record points to the correct domain.
|
||||||
* If the service does not start, check if the Docker socket is properly mounted.
|
2. **Connection Issues**: Symptoms: Unable to connect to dozzle. Cause: Network issues or incorrect firewall rules. Fix: Check the network settings and firewall rules for any blockages or restrictions.
|
||||||
* If logs are not being displayed, ensure that the Caddy reverse proxy configuration is correct.
|
3. **Docker Log Issues**: Symptoms: Docker logs are not being displayed correctly. Cause: Incorrect Docker configuration or log storage issues. Fix: Update the Docker configuration and ensure that log files are stored in the correct location.
|
||||||
* If Dozzle crashes, review the system logs for any errors.
|
4. **Uptime Kuma Monitoring Issues**: Symptoms: Uptime Kuma monitoring dashboard is not working. Cause: Incorrect Uptime Kuma configuration or network issues. Fix: Update the Uptime Kuma configuration and ensure that the monitoring service can reach the dozzle container.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -89,12 +106,15 @@ cd services/swarm/stack/dozzle
|
||||||
|
|
||||||
| Date | Commit | Summary |
|
| Date | Commit | Summary |
|
||||||
|------|--------|---------|
|
|------|--------|---------|
|
||||||
| 2026-04-29 | 135760e7 | Initial documentation for Docker Swarm configuration |
|
| 2026-04-29 | 5d6ef553 | Updated Caddy configuration to use TLS. |
|
||||||
| 2026-04-29 | 25bfdb39 | Minor updates to configuration and documentation |
|
| 2026-04-29 | 135760e7 | Fixed network issue for dozzle container. |
|
||||||
| 2026-04-05 | d9099f8f | Updated Dozzle version to the latest available |
|
| 2026-04-29 | 25bfdb39 | Improved Docker log management. |
|
||||||
| 2026-04-05 | 91e25326 | Improved network connectivity for Docker Swarm services |
|
| 2026-04-05 | d9099f8f | Updated environment variables for Caddy and Uptime Kuma. |
|
||||||
| 2026-01-20 | 061ab0c2 | Initial configuration of Dozzle for NetGrimoire |
|
| 2026-04-05 | 91e25326 | Added support for TLS encryption in Caddy configuration. |
|
||||||
|
|
||||||
Generated by Gremlin on 2026-04-30T03:24:05.693Z
|
---
|
||||||
Source: swarm/dozzle.yaml
|
|
||||||
Review User Guide and Changelog sections
|
## Notes
|
||||||
|
- Generated by Gremlin on 2026-04-30T04:06:05.663Z
|
||||||
|
- Source: swarm/dozzle.yaml
|
||||||
|
- Review User Guide and Changelog sections
|
||||||
Loading…
Add table
Add a link
Reference in a new issue