NextCloud AIO borg backup not wokring

just deployed AIO which went fine and everything came up without issue.. Was able to log in make sure I didnt have any errors etc but after I made it through that I wanted to double check I could get a good backup using borg before moving forward and ran into an issue.. Looks like Borg is having an issue coming up and will not backup my env..

Here is the log from the master container

Trying to fix docker.sock permissions internally…
Creating docker group internally with id 996
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
:warning: Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
INF INF INF INF INF INF INF INF ts=1746888386.5691683 INF INF INF INF INF INF INF INF ts=1746888386.5691683 msg=using config from file INF INF INF INF INF INF INF INF ts=1746888386.5691683 INF INF INF INF INF INF INF INF ts=1746888386.5691683 msg=using config from file file=/Caddyfile
[Sat May 10 14:46:26.572300 2025] [mpm_event:notice] [pid 144:tid 144] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.3 configured – resuming normal operations
INF INF INF INF INF INF INF INF ts=1746888386.5731683 INF INF INF INF INF INF INF INF ts=1746888386.5731683 msg=adapted config to JSON INF INF INF INF INF INF INF INF ts=1746888386.5731683 INF INF INF INF INF INF INF INF ts=1746888386.5731683 msg=adapted config to JSON adapter=caddyfile
[Sat May 10 14:46:26.573189 2025] [core:notice] [pid 144:tid 144] AH00094: Command line: ‘httpd -D FOREGROUND’
[10-May-2025 14:46:26] NOTICE: fpm is running, pid 150
[10-May-2025 14:46:26] NOTICE: ready to handle connections
NOTICE: PHP message: Slim Application Error
Type: Exception
Code: 0
Message: Could not start container nextcloud-aio-borgbackup: {“message”:“error gathering device information while adding custom device "/dev/fuse": no such file or directory”}
File: /var/www/docker-aio/php/src/Docker/DockerActionManager.php

6
Trace: #0 /var/www/docker-aio/php/src/Controller/DockerController.php(59): AIO\Docker\DockerActionManager->StartContainer(Object(AIO\Container\Container))
#1 /var/www/docker-aio/php/src/Controller/DockerController.php(95): AIO\Controller\DockerController->PerformRecursiveContainerStart(‘nextcloud-aio-b…’)
#2 /var/www/docker-aio/php/src/Controller/DockerController.php(82): AIO\Controller\DockerController->startBackup()
#3 /var/www/docker-aio/php/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(38): AIO\Controller\DockerController->StartBackupContainerBackup(Object(GuzzleHttp\Psr7\ServerRequest), Object(GuzzleHttp\Psr7\Response), Array)
#4 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/Route.php(363): Slim\Handlers\Strategies\RequestResponse->__invoke(Array, Object(GuzzleHttp\Psr7\ServerRequest), Object(GuzzleHttp\Psr7\Response), Array)
#5 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Slim\Routing\Route->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#6 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#7 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/Route.php(321): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#8 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/RouteRunner.php(74): Slim\Routing\Route->run(Object(GuzzleHttp\Psr7\ServerRequest))
#9 /var/www/docker-aio/php/vendor/slim/csrf/src/Guard.php(482): Slim\Routing\RouteRunner->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#10 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(177): Slim\Csrf\Guard->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Slim\Routing\RouteRunner))
#11 /var/www/docker-aio/php/vendor/slim/twig-view/src/TwigMiddleware.php(117): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#12 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Views\TwigMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#13 /var/www/docker-aio/php/src/Middleware/AuthMiddleware.php(36): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#14 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(280): AIO\Middleware\AuthMiddleware->__invoke(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#15 /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(77): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#16 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Middleware\ErrorMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#17 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#18 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(209): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#19 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(193): Slim\App->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#20 /var/www/docker-aio/php/public/index.php(189): Slim\App->run()
#21 {main}
Tips: To display error details in HTTP response set “displayErrorDetails” to true in the ErrorHandler constructor.

Hi, see GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

Thank you and yes I figured it out.. Looks like a fuse issue with running this in an LXC container, this error went away after adding the fuse feature in options via proxmox.. Also figured out that mounting the data dir with NFS breaks backups as well.. ended up just using SMB / CIFS and everything is working now :slight_smile: