tomspark wrote:
Short version: SparkBox can't "adopt" an external instance of anything — the dashboard tiles, health checks, and auto-config (pihole blocklists, portainer admin-password seeding) are all wired to its own managed containers. There's no point-at-existing toggle. But your two cases differ: Pi-hole: it's a standalone opt-in module. Just don't enable it (deselect it in sudo sparkbox config). Your existing Pi-hole keeps running untouched and SparkBox won't spawn a duplicate or fight you for port 53. Portainer: this one's baked into SparkBox's core stack, not individually toggleable. Cleanest path is to just let SparkBox's Portainer run — it's ~50MB and only manages SparkBox's own containers, which is actually useful separation from your main one. The only real friction is if both bind the same ports (9000/9443). Tell me what ports your existing Portainer is on and I'll show you how to remap SparkBox's so they coexist cleanly.