Migrate Docker containers to dedicated VM

Architecture changes:
- Created VM 100 "docker-services" (Debian 12 Cloud Image)
- 10GB RAM, 6 Cores, 50GB system disk
- Separate 100GB LVM data volume for service data
- WireGuard moved from host to VM (10.0.0.2)
- All containers migrated and running

Updated documentation to reflect new architecture

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Martin Eckardt
2025-12-28 21:04:47 +01:00
parent 3f74077c3e
commit 64bcc0091a
8 changed files with 793 additions and 2 deletions

View File

@@ -15,9 +15,14 @@ Internet
|
| WireGuard Tunnel (10.0.0.0/24)
v
[Proxmox: 192.168.178.111 / 10.0.0.2]
[Proxmox: 192.168.178.111]
- Hypervisor
|
v
[VM 100 "docker-services": 192.168.178.200 / 10.0.0.2]
- Docker Host
- Alle Services als Container
- 50GB System + 100GB Data Volume
```
## Services
@@ -202,4 +207,9 @@ Siehe [docs/TROUBLESHOOTING.md](docs/TROUBLESHOOTING.md) fuer:
- WireGuard + Fail2Ban Integration
- Separates Git-Repository: proxmox-netdata
- VT-x im BIOS aktiviert fuer VM-Support
- VM 100 "docker-services" vorbereitet (Debian 12 Cloud Image)
- Docker Container Migration zu VM 100:
- VM erstellt: 10GB RAM, 6 Cores, 50GB System Disk
- Separates 100GB Data Volume fuer Nextcloud/Services
- WireGuard auf VM konfiguriert (10.0.0.2)
- Alle Container erfolgreich migriert
- Alte Container auf Host gestoppt