Loading blog posts...
Loading blog posts...
Loading...

Pi-hole’s security fixes and GlitchTip’s retention changes make the week of 20 November 2026 a poor time for blind container updates. This edition of Best Self-Hosted looks at which releases reduce operational work and which need a migration plan before you pull the image.
Quick summary
The releases and announcements cover November 6 through November 20. They don’t include verified GitHub star counts or weekly growth, so this is an operational shortlist.
| Tool | Best for | Price | Standout feature |
|---|---|---|---|
| Pi-hole | Network-wide DNS filtering | Not stated in cited source | Security fixes in the November Docker image |
| Unraid | Managing a container-heavy home server | Not stated in cited source | Preserves multiple Docker network attachments |
| Patchboard | Shared container troubleshooting | Not stated in cited source | Connects container faults, logs, and repair controls |
| Nginx UI | Managing Nginx and certificates | Not stated in cited source | Independently updated DNS certificate plugins |
| NetBird | Private network access with controlled automation | Not stated in cited source | Optional MCP endpoint with read-only OAuth access by default |
| boxd | Offloading coding-agent builds | Not stated in cited source | Separate remote execution environments per Git worktree |
| GlitchTip | Self-hosted error tracking | Not stated in cited source | Reworked stack-trace processing |
| Cap | Self-hosted CAPTCHA infrastructure | Not stated in cited source | Per-request analytics with ClickHouse or DuckDB |
The sources don’t establish comparable pricing. Check current licensing and deployment costs; self-hosted doesn’t mean free.
Pi-hole provides network-wide DNS filtering. Its November release announcement documents security fixes that deserve priority over the convenience features elsewhere in this list.
2026.11.0, containing FTL 6.9 and Core 6.6.Both components fix command execution through files.gravity. Core’s installer also writes files into /etc/pihole as the pihole user to address unsafe file handling.
Patch this before adding another dashboard. Check the versions actually running after deployment; a successful image pull doesn’t mean the service was replaced.
Unraid’s release announcement and the Patchboard README describe two ways to reduce container-maintenance work: preserving configuration during updates and bringing troubleshooting controls together.
7.4.0, released November 10.latest-slim image cannot update containers.Unraid manages server storage and applications. It now preserves multiple custom Docker network attachments through container updates and recreation. Its Advanced View also adds a Memory limit field directly to the container form.
Patchboard discovers applications through the Docker socket and connects faults with logs and repair controls in a shared dashboard. That’s useful when troubleshooting means jumping between a dashboard, a terminal, and individual application pages. Docker socket access makes it a privileged operational component.
Prioritize Unraid’s update on an existing Unraid server before introducing another management layer. If you deploy Patchboard, choose its image deliberately: the slim variant excludes the Docker CLI, so it cannot provide container-update controls.
Nginx UI is a web interface for managing Nginx. Version 3.0.0 moves DNS certificate providers out of the core application.
For a wildcard certificate validated through your DNS provider, the integration now lives in a plugin that can update independently. DNS-01 proves domain control through a DNS record, so provider compatibility directly affects certificate issuance and renewal.
The independent update path is the win, though it adds another component to track. Separate processes don’t make plugins safe to treat as untrusted code. After upgrading, confirm the relevant provider plugin is installed and test certificate renewal before the next unattended run.

NetBird connects machines through a private network. Its version 0.83.0 release adds an optional Model Context Protocol server, an interface through which AI clients can call exposed tools.
NB_MCP_ENABLED=true exposes /api/mcp.NB_MCP_TOOLS restricts the available tools.Start with inspection. The release keeps OAuth connections read-only unless the user grants write access. Leave write access disabled during an initial trial and restrict the tool list to the task being tested.
The permissions concern from the August agent-project roundup applies here too: read-only access still exposes information, so review authentication and scope.
boxd runs build commands on a remote Linux host, using a separate rootless Podman container for each Git worktree, according to its project README.
--vm selects a virtual machine for work needing Docker or root.A coding agent can run tests remotely in its worktree’s execution environment, separate from concurrent tasks. Persistent caches avoid starting every build from an empty environment.
Rootless containers are a sensible default for ordinary build work. They aren’t interchangeable with virtual machines; boxd offers the latter for tasks that need Docker or root.
Try it first on a repository with a repeatable test suite and no production credentials. Confirm the test result and cache behavior before moving sensitive build workflows onto the host.

GlitchTip provides error tracking; Cap provides CAPTCHA infrastructure. Both require configuration work beyond replacing an image, as documented in the GlitchTip announcement and Cap release notes.
7.0 needs PostgreSQL 15 or newer.GlitchTip rebuilds stack-trace processing and changes permissions, but the urgent upgrade detail is retention. Rename GLITCHTIP_MAX_EVENT_LIFE_DAYS to GLITCHTIP_RETENTION_DAYS; retired settings are ignored, potentially restoring the 90-day default and deleting older events.
Verify the database version, inspect the effective retention configuration, and review permission changes before production rollout.

Cap’s capd version 4.0.0 adds per-request analytics backed by ClickHouse or DuckDB. Upgrading from the previous major version requires resetting site secrets, API keys, and dashboard sessions, plus adding persistent storage at /usr/src/app/data.
Those resets affect applications consuming Cap as well as its dashboard. Schedule the migration with the people responsible for those integrations, and confirm the data volume exists before treating the replacement server as ready.
6.9 and Core 6.6, the versions bundled in Docker image 2026.11.0.15 and replace the retired retention variable./usr/src/app/data and list every integration needing replacement credentials.NB_MCP_TOOLS.latest-slim.Patch Pi-hole, protect GlitchTip’s retained data, and plan Cap’s credential changes first. Then spend your experimentation time on tools that remove a specific operational burden from your server.