333bb82c162860ec39e0e5ed926a91c0754a548c
Found via live testing on docker-2 after merging #19: git-guard.sh is tracked in git at mode 100644 (not executable). stack-deploy.sh correctly invokes it as `bash deploy/git-guard.sh`, sidestepping the exec bit for the first call -- but the script's own internal `exec "$0" "$@"` calls (used to cleanly re-run after a successful push or stash-pop) rely on the kernel executing the file directly, which requires +x. Since every fresh checkout or fast-forward preserves the tracked 644 mode, this failed with "Permission denied" (exit 126) the moment either self-re-invocation path was actually exercised. Confirmed via a live dry run: simulated the exact #18 incident shape (dirty git-guard.sh on a HEAD 3 commits behind origin/main) on docker-2. The new stash-first logic from #19 worked perfectly end-to-end -- detected dirty+stale, stashed safely, fast-forwarded via resync_with_origin(), and popped the stash cleanly -- but then hit this pre-existing bug on the final `exec "$0" "$@"` re-invocation. This bug pre-dates #19 (the old dirty-commit-then-push-success path had the identical pattern); #19 just added a second trigger point that happened to surface it during testing. Fix: `exec bash "$0" "$@"` explicitly invokes through the interpreter instead of relying on the file's own execute bit -- correct regardless of what git tracks the file's mode as.
Homelab Infrastructure Repository - Docker Swarm Compose Files
This Gitea repository contains Docker Swarm compose files for all services running in the homelab.
For operational scripts (backup hooks, prune watchdog, network configuration), see the separate homelab-scripts repository.
📁 Directory Structure
├── traefik.yaml # Reverse proxy & load balancer
├── auth.yaml # Authentik authentication
├── postgresql.yaml # PostgreSQL database
├── maintenance.yaml # Cronicle scheduler, Uptime Kuma
├── ... (other service stacks)
└── README.md # This file
🚀 Quick Start
Deploy a Stack
# SSH into a Docker LXC (docker-1, docker-2, or docker-3)
ssh root@docker-1
# Clone this repo locally
cd /volume1/docker
git clone https://git.bryanmail.net/admin/compose-files.git repo
cd repo
# Deploy a stack
docker stack deploy -c traefik.yaml traefik
docker stack deploy -c auth.yaml auth
docker stack deploy -c postgresql.yaml postgresql
Update a Stack
# Pull latest changes
git pull origin main
# Re-deploy (applies changes)
docker stack deploy -c traefik.yaml traefik
# View status
docker stack ps traefik
docker service ls
Remove a Stack
docker stack rm traefik
📋 Available Stacks
| Stack | File | Purpose |
|---|---|---|
| Traefik | traefik.yaml | Reverse proxy, load balancer, TLS termination |
| Authentik | auth.yaml | Authentication & authorization |
| PostgreSQL | postgresql.yaml | Database backend |
| Maintenance | maintenance.yaml | Cronicle jobs, Uptime Kuma monitoring |
| ... | ... | (Add more as you create them) |
🛠️ Common Tasks
Deploy a New Service
- Create compose file in this repo:
myservice.yaml - Test locally (on single host):
docker-compose -f myservice.yaml up -d - Convert to Swarm format (remove
container_name, useservices:for Swarm) - Deploy to Swarm:
docker stack deploy -c myservice.yaml myservice - Commit & push:
git add myservice.yaml git commit -m "Add myservice stack" git push origin main
Check Service Status
# List all services
docker service ls
# Get details about a service
docker service inspect traefik_reverse-proxy
# View service logs
docker service logs -f traefik_reverse-proxy
# Check tasks (containers)
docker service ps traefik_reverse-proxy
Monitor Disk Space
df -h /volume1/docker-root
# Docker prune watchdog handles auto-cleanup (see homelab-scripts repo)
🔐 Secrets Management
DO NOT commit secrets, passwords, or API keys to this repo.
Use one of these approaches:
Option 1: Docker Secrets (Recommended for Swarm)
services:
myapp:
secrets:
- db_password
secrets:
db_password:
external: true
Create the secret:
echo "mysecretpassword" | docker secret create db_password -
Option 2: Environment Files (Not tracked by git)
# Create .env (add to .gitignore)
echo "DB_PASSWORD=mysecretpassword" > .env
# Use in compose
env_file: .env
📚 Architecture
Swarm Cluster
nuck7-1 (Hypervisor) nuck7-2 (Hypervisor) nuck7-3 (Hypervisor)
├─ docker-1 (LXC 4031) ├─ docker-2 (LXC 4032) ├─ docker-3 (LXC 4033)
│ └─ Swarm Manager │ └─ Swarm Leader │ └─ Swarm Manager
└─ ... └─ ... └─ ...
Storage
- CephFS mounted at
/volume1/docker/(shared across all nodes) - Compose files:
/volume1/docker/compose-files/ - Service data: Named volumes or
/volume1/docker/mounts
Networking
- VIP: 192.168.4.30 (Keepalived)
- Docker hosts: 192.168.4.31-33
- Traefik: Reverse proxy with Let's Encrypt TLS
- Domain: bryanmail.net
🔗 Related Repositories
- homelab-scripts - Operational scripts (backup hooks, monitoring, network config)
- Proxmox MCP Setup - Documented in notes
- Architecture Decision Records (ADRs) - Documented in notes
🐛 Troubleshooting
Stack won't deploy
# Check syntax
docker-compose config -f myservice.yaml
# Check node availability
docker node ls
# Check disk space
df -h /volume1/docker-root
Service keeps crashing
# View logs
docker service logs -f myservice_name
# Inspect container
docker ps -a | grep myservice
Network issues
# List networks
docker network ls --filter driver=overlay
# Test connectivity
docker run --rm --network traefik_backend alpine ping traefik_reverse-proxy
📞 Contributing
When adding new services:
- Use Swarm-compatible YAML (no
container_name) - Document requirements in compose file comments
- Test on non-production first
- Add notes about volumes, secrets, networking
- Update this README with stack description
📝 Git Workflow
# Before starting work
git pull origin main
# Create feature branch for new service
git checkout -b feature/new-service
# Make changes and commit
git add .
git commit -m "Add new-service stack"
# Push
git push origin feature/new-service
Version Control Best Practices
- Keep compose files in sync with deployed state
- Pin image versions (avoid
latesttag) - Document breaking changes in commit messages
- Use meaningful commit messages for audit trail
Languages
Shell
77.6%
Python
22.4%