[GH-ISSUE #5728] Feature Request: Netbird client as Nextcloud AIO community container #11698

Open
opened 2026-08-05 01:30:32 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @renne on GitHub (Mar 29, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5728

Is your feature request related to a problem? Please describe.

Self-hosters running Nextcloud All-In-One (AIO) want to access their Nextcloud instance remotely — or expose it to family, friends, or a small team — without opening ports in their router, obtaining a static public IP, or setting up a dedicated VPS with a traditional reverse proxy. Today there is no first-party solution that integrates Netbird with the AIO ecosystem, so users must either manually run a separate Netbird container and wire it into the AIO network by hand, or fall back to less-secure solutions (DDNS + port-forwarding, Cloudflare Tunnel, etc.).

Describe the solution you'd like

Provide an official Nextcloud AIO community container that runs a Netbird client. The community container would:

  1. Join the user's Netbird overlay network using a setup key — no manual Docker networking required.
  2. Expose the Nextcloud AIO stack (and optionally other community containers running in the same AIO instance) through the Netbird mesh, so any other Netbird peer (phone, laptop, family member's device) can reach Nextcloud securely without any port-forwarding or public IP.
  3. Support the Netbird routing-peer pattern — users who want full public-internet access can point a cheap VPS peer (also running Netbird) as a routing peer / ingress, keeping Nextcloud behind the firewall while still serving a public domain over HTTPS.

The community container spec is a straightforward JSON spec + readme.md contribution to the nextcloud/all-in-one repository, but an official or blessed container image from the Netbird team would give users confidence in the integration.

Describe alternatives you've considered

  • Manual Netbird container alongside AIO – works but requires users to understand Docker networking, manually attach the Netbird container to the AIO Docker network, and maintain the setup across AIO updates. High barrier for non-technical users.
  • Cloudflare Tunnel (cloudflared) – a popular choice for exposing self-hosted services without port-forwarding, but routes all traffic through Cloudflare's servers, which is unsuitable for privacy-conscious users. Netbird is the self-hosted alternative.
  • WireGuard directly – similar complexity as the manual approach; no mesh management UI.
  • Tailscale – a competing product. Netbird is the fully self-hostable, open-source alternative. Neither Tailscale nor Netbird currently has a community container in the AIO repo — this feature request would make Netbird the first.

Additional context

Nextcloud is one of the most popular self-hosted applications with a large and active community (millions of users, active forums, dedicated conferences). Shipping an official Netbird AIO community container would:

  • Serve as highly effective advertising for Netbird inside the Nextcloud ecosystem — every AIO user who sets up the container becomes a Netbird user and potential advocate.
  • Lower the barrier to adoption for non-technical self-hosters who trust the AIO project's curated community containers.
  • Demonstrate Netbird as the go-to self-hosted alternative to Tailscale/Cloudflare Tunnel for secure remote access.
  • Complement a potential Nextcloud + Netbird OIDC setup by making it easy to deploy both services together.

Reference community-container examples in nextcloud/all-in-one:

  • caddy — custom reverse proxy (network-layer integration example)
  • npmplus — Nginx Proxy Manager Plus (another network-layer container)

Each community container consists of a JSON spec file and a readme.md in its own subdirectory — a minimal, well-documented contribution. A Netbird community container following this same pattern would be a natural fit and a meaningful step toward broader adoption.

Originally created by @renne on GitHub (Mar 29, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5728 **Is your feature request related to a problem? Please describe.** Self-hosters running [Nextcloud All-In-One (AIO)](https://github.com/nextcloud/all-in-one) want to access their Nextcloud instance remotely — or expose it to family, friends, or a small team — without opening ports in their router, obtaining a static public IP, or setting up a dedicated VPS with a traditional reverse proxy. Today there is no first-party solution that integrates Netbird with the AIO ecosystem, so users must either manually run a separate Netbird container and wire it into the AIO network by hand, or fall back to less-secure solutions (DDNS + port-forwarding, Cloudflare Tunnel, etc.). **Describe the solution you'd like** Provide an official [Nextcloud AIO community container](https://github.com/nextcloud/all-in-one/tree/main/community-containers) that runs a Netbird client. The community container would: 1. **Join the user's Netbird overlay network** using a setup key — no manual Docker networking required. 2. **Expose the Nextcloud AIO stack** (and optionally other community containers running in the same AIO instance) through the Netbird mesh, so any other Netbird peer (phone, laptop, family member's device) can reach Nextcloud securely without any port-forwarding or public IP. 3. **Support the Netbird routing-peer pattern** — users who want full public-internet access can point a cheap VPS peer (also running Netbird) as a routing peer / ingress, keeping Nextcloud behind the firewall while still serving a public domain over HTTPS. The community container spec is a straightforward JSON spec + readme.md contribution to the [nextcloud/all-in-one](https://github.com/nextcloud/all-in-one/tree/main/community-containers) repository, but an official or blessed container image from the Netbird team would give users confidence in the integration. **Describe alternatives you've considered** - **Manual Netbird container alongside AIO** – works but requires users to understand Docker networking, manually attach the Netbird container to the AIO Docker network, and maintain the setup across AIO updates. High barrier for non-technical users. - **Cloudflare Tunnel (cloudflared)** – a popular choice for exposing self-hosted services without port-forwarding, but routes all traffic through Cloudflare's servers, which is unsuitable for privacy-conscious users. Netbird is the self-hosted alternative. - **WireGuard directly** – similar complexity as the manual approach; no mesh management UI. - **Tailscale** – a competing product. Netbird is the fully self-hostable, open-source alternative. Neither Tailscale nor Netbird currently has a community container in the AIO repo — this feature request would make Netbird the first. **Additional context** Nextcloud is one of the most popular self-hosted applications with a large and active community (millions of users, active forums, dedicated conferences). Shipping an official Netbird AIO community container would: - **Serve as highly effective advertising for Netbird** inside the Nextcloud ecosystem — every AIO user who sets up the container becomes a Netbird user and potential advocate. - Lower the barrier to adoption for non-technical self-hosters who trust the AIO project's curated community containers. - Demonstrate Netbird as the go-to self-hosted alternative to Tailscale/Cloudflare Tunnel for secure remote access. - Complement a potential Nextcloud + Netbird OIDC setup by making it easy to deploy both services together. Reference community-container examples in nextcloud/all-in-one: - [`caddy`](https://github.com/nextcloud/all-in-one/tree/main/community-containers/caddy) — custom reverse proxy (network-layer integration example) - [`npmplus`](https://github.com/nextcloud/all-in-one/tree/main/community-containers/npmplus) — Nginx Proxy Manager Plus (another network-layer container) Each community container consists of a JSON spec file and a readme.md in its own subdirectory — a minimal, well-documented contribution. A Netbird community container following this same pattern would be a natural fit and a meaningful step toward broader adoption.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11698