Pihole / Raspberry Pi Documentation
Secondary server — a Raspberry Pi that supports the main ../homelab/README in various ways.
Quick Reference
| Property | Value |
|---|---|
| Tailscale IP | 100.89.172.56 |
| Tailscale Hostname | (on bunny-wyvern.ts.net) |
| Connection to Dockhand | Hawser agent (env=2) |
| Docker Files | /home/artanis/ (Desktop + TS_KH_Bridge dirs) |
Hardware details (CPU, RAM, model) are not yet documented. To be filled in.
Stacks
| Stack | Status | Purpose |
|---|---|---|
| stacks/home_assistant | Running | Home automation |
| stacks/ts_kh_bridge | Stopped | Tailscale inter-tailnet bridge |
| stacks/portainer_agent | Running | Portainer remote agent |
How It Supports the Homelab
- Home Assistant — Home automation hub; runs on the Pi for low-power always-on operation and USB device access (Zigbee/Z-Wave stick on
/dev/ttyUSB0) - Tailscale Bridge — Bridges two separate Tailnets together (
Home↔KH) — currently stopped - Portainer Agent — Allows a Portainer instance (elsewhere) to manage this Pi's Docker remotely
Key Differences from Homelab
- No centralized
DockerFilesdirectory — compose files are scattered across~/Desktop/and~/TS_KH_Bridge/ - Home Assistant uses
network_mode: host(full host network) for mDNS/Bluetooth/Zigbee discovery - Much lighter workload — only 3 stacks, 5 containers total
- Pihole (DNS/ad-blocking) likely runs natively on the Pi OS, not in Docker — no container found for it