From my perspective, the whole idea of running Nextcloud AIO inside an LXC container does not really seem like a suitable approach from the beginning.
This is just my personal opinion based on experience and what I’ve seen repeatedly on the forum.
Nextcloud AIO is not a simple containerized app – it is a Docker-based orchestration stack that manages multiple services, performs self-checks, networking validation, certificate handling, and relies heavily on predictable system behavior. In this context, LXC introduces an additional abstraction layer that often leads to edge cases.
Looking through similar topics, there is a clear pattern with LXC setups:
-
Docker inside LXC can lead to compatibility issues (namespaces, cgroups, nested container behavior)
-
Permission problems related to UID/GID mapping are quite common
-
Storage and bind-mount inconsistencies can appear, especially after restores
-
Networking can behave unpredictably (reverse proxy loops, unreachable services, hairpin NAT issues)
-
Some features (e.g. Collabora, TURN/HPB) may not work reliably
Even if everything “works”, it often ends up being fragile and difficult to debug.
On the other hand, the official AIO documentation and guides consistently assume a deployment on a dedicated VM, VPS, or bare metal system. LXC is not mentioned as a supported runtime, which suggests it is more of a workaround than a design target.
Another important point is that AIO is designed around Docker running with root-level access (it does not support PUID/PGID), which further reinforces that it expects a full environment rather than a restricted container layer like LXC (if I am not mistaken).
Because of all this, I would personally consider LXC + AIO as a non-ideal combination. It may run, but issues like extremely long startup times, timeouts, or inconsistent behavior are not surprising in that setup.
If stability and predictability are the goal, running AIO inside a VM (for example Ubuntu Server) aligns much better with how it is designed to operate.
For reference, this is exactly the approach I am using in my own setup, which is based on Proxmox with a clean separation between services (Nginx Proxy Manager and Nextcloud AIO), each running in its own environment:
https://help.nextcloud.com/t/proxmox-nginx-nextcloud-aio-watchtower-deployment-guide/233643
This setup avoids the complexity of nested container layers and has proven to be stable and predictable in the long run.