This page documents the Docker service fixes applied to the Lucille4 homelab server and tracks known non-critical issues for monitoring purposes.
The MetaMCP service experienced database initialization issues that have been resolved:
projects, codes) causing service startup failuresmcp_servers_url_check constraintFor future MetaMCP deployments, see the MetaMCP configuration guide for proper initialization steps.
These issues are being monitored but do not impact core functionality:
lucille3:7007X-Forwarded-Host headersVarious services report minor warnings about:
These do not affect core functionality and are expected in a Docker environment.
When troubleshooting Docker services on Lucille4:
docker logs <container-name>docker ps and check STATUS column.envMerged from docker-fixes-wiki.md on 2025-07-01
This document tracks fixes applied to Docker services on Lucille4 and documents known non-critical issues that are being monitored. It serves as a reference for troubleshooting and maintaining service health.
Problem: MetaMCP service was failing to start due to missing database tables and constraints.
Solution Applied:
projects, codes)mcp_servers_url_check constraintResult: MetaMCP service now running successfully without database errors.
These issues are being monitored but do not impact core functionality:
Issue: Cannot connect to lucille3:7007 for remote container monitoring
Impact: Low - Only affects ability to monitor lucille3 containers from lucille4
Expected Behavior: This is normal when:
Action: No action needed unless lucille3 monitoring is required
Issue: Cannot validate Paperless API connection (502 Bad Gateway)
Impact: Medium - AI features for Paperless document processing unavailable
Potential Causes:
Action Items:
Note: Core Paperless functionality remains unaffected
Issue: Warnings about unnecessary X-Forwarded-Host headers
Impact: None - Purely cosmetic warnings
Details: Caddy automatically manages forwarded headers, making manual header configuration redundant
Recommended Fix:
## Remove explicit header configurations that Caddy handles automatically
## X-Forwarded-Host is passed automatically by reverse_proxy
Issue: Memory overcommit warnings in Redis containers
Impact: None in normal operation
Details: Common warning in containerized environments due to kernel memory overcommit settings
Optional Fix (requires host access):
## Add to host system /etc/sysctl.conf
vm.overcommit_memory = 1
## Apply changes
sudo sysctl -p
Various Services: Missing optional configuration files or deprecated settings
Impact: None - Services function normally
Examples:
Action: Monitor during updates, address if functionality is affected
## Check all service statuses
docker compose ps
## View recent logs for errors
docker compose logs --tail=50 | grep -i error
## Monitor resource usage
docker stats --no-stream
## Individual service status
docker compose ps [service_name]
## Service logs
docker compose logs -f [service_name] --tail=100
## Resource usage
docker stats [container_name]
## Test PostgreSQL connection
docker compose exec postgres psql -U postgres -c "SELECT 1"
## Check Redis connectivity
docker compose exec redis redis-cli ping
## List networks
docker network ls
## Inspect network configuration
docker network inspect homelab-lucille4_caddy
## Test internal connectivity
docker compose exec [service] ping [target_service]
Last Updated: {{date}}
Category: Homelab / Servers / Lucille4 / Operations