Hi,
I have tried so many things now but so far I cannot get NextcloudAIO to get past the Container Starting Up part of the setup. It seems as though Postgres just keeps restarting. I am going to install it on a clean system now and will write up my steps. Note that I am using Nginx Proxy Manager which has been set up with the URL and the OpenMediaVault IP, and port 11000
- In OMV Web Ui for to Services | Compose | Files and click + to add a file
- Name NerdcloudAIO
- paste in compose code
version: "3.8"
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer
services:
nextcloud:
image: nextcloud/all-in-one:latest
restart: always
container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not wo>
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the >
- /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the app>
ports:
- 14010:8080
environment:
- APACHE_PORT=11000
- Click Save
- Select NerdcloudAIO and click pull (everything seems to be being pulled and job completes). Click close on dialog box
- Click up (runs ‘docker-compose up -d’)
7.Firefox browser, go to https://IP:14010 - Page is rendered Nextcloud AIO setup which gives me the password (several words). Copy those, paste into secure notepad for later)
- Click Open Nextcloud AIO Login
- Paste password onto box on Nextcloud AIO Login page and click log in.
- Type in my domain and click Submit Domain (wait about 30 seconds), goes to /containers URL.
- Check Collabora, Fulltextsearch, Imaginary and Save Changes
- Enter Timezone and click Submit timezone
- Click ‘Download and start containers’
- Message pops up about issue in mastercontainer
- Run
sudo docker logs -f nextcloud-aio-mastercontainer
Output is
Trying to fix docker.sock permissions internally...
Creating docker group internally with id 992
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
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
{"level":"info","ts":1695258347.1354985,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""}
[21-Sep-2023 01:05:47] NOTICE: fpm is running, pid 121
[21-Sep-2023 01:05:47] NOTICE: ready to handle connections
[Thu Sep 21 01:05:47.166245 2023] [mpm_event:notice] [pid 115:tid 140006916660040] AH00489: Apache/2.4.57 (Unix) OpenSSL/3.1.2 configured -- resuming normal operations
[Thu Sep 21 01:05:47.166714 2023] [core:notice] [pid 115:tid 140006916660040] AH00094: Command line: 'httpd -D FOREGROUND'
NOTICE: PHP message: Slim Application Error
Type: AIO\Data\InvalidSettingConfigurationException
Code: 0
Message: /mnt/docker-aio-config/data/ does not have enough space for writing the config file! Not writing it back!
File: /var/www/docker-aio/php/src/Data/ConfigurationManager.php
Line: 520
Trace: #0 /var/www/docker-aio/php/src/Data/ConfigurationManager.php(39): AIO\Data\ConfigurationManager->WriteConfig(Array)
#1 /var/www/docker-aio/php/src/Docker/DockerActionManager.php(248): AIO\Data\ConfigurationManager->GetAndGenerateSecret('REDIS_PASSWORD')
#2 /var/www/docker-aio/php/src/Controller/DockerController.php(47): AIO\Docker\DockerActionManager->CreateContainer(Object(AIO\Container\Container))
#3 /var/www/docker-aio/php/src/Controller/DockerController.php(33): AIO\Controller\DockerController->PerformRecursiveContainerStart('nextcloud-aio-r...', true)
#4 /var/www/docker-aio/php/src/Controller/DockerController.php(33): AIO\Controller\DockerController->PerformRecursiveContainerStart('nextcloud-aio-n...', true)
#5 /var/www/docker-aio/php/src/Controller/DockerController.php(193): AIO\Controller\DockerController->PerformRecursiveContainerStart('nextcloud-aio-a...', true)
#6 /var/www/docker-aio/php/src/Controller/DockerController.php(173): AIO\Controller\DockerController->startTopContainer(true)
#7 /var/www/docker-aio/php/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(38): AIO\Controller\DockerController->StartContainer(Object(GuzzleHttp\Psr7\ServerRequest), Object(GuzzleHttp\Psr7\Response), Array)
#8 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/Route.php(358): Slim\Handlers\Strategies\RequestResponse->__invoke(Array, Object(GuzzleHttp\Psr7\ServerRequest), Object(GuzzleHttp\Psr7\Response), Array)
#9 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(65): Slim\Routing\Route->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#10 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(65): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#11 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/Route.php(315): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#12 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/RouteRunner.php(68): Slim\Routing\Route->run(Object(GuzzleHttp\Psr7\ServerRequest))
#13 /var/www/docker-aio/php/vendor/slim/csrf/src/Guard.php(476): Slim\Routing\RouteRunner->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#14 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(168): Slim\Csrf\Guard->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Slim\Routing\RouteRunner))
#15 /var/www/docker-aio/php/vendor/slim/twig-view/src/TwigMiddleware.php(115): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#16 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(121): Slim\Views\TwigMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#17 /var/www/docker-aio/php/src/Middleware/AuthMiddleware.php(38): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#18 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(269): AIO\Middleware\AuthMiddleware->__invoke(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#19 /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(76): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#20 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(121): Slim\Middleware\ErrorMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#21 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(65): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#22 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(199): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#23 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(183): Slim\App->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#24 /var/www/docker-aio/php/public/index.php(182): Slim\App->run()
#25 {main}
Tips: To display error details in HTTP response set "displayErrorDetails" to true in the ErrorHandler constructor.
Noted this error
Message: /mnt/docker-aio-config/data/ does not have enough space for writing the config file! Not writing it back!
File: /var/www/docker-aio/php/src/Data/ConfigurationManager.php
Line: 520
I’ve searched and cannot find anyone else having this issue.
I have no idea what is running out of space as OMV has nearly 10tb of which only 3tb are used.
If I run df -h
then I get this
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 2.5M 3.2G 1% /run
/dev/sda1 6.9G 6.5G 0 100% /
tmpfs 16G 84K 16G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 16G 8.0K 16G 1% /tmp
/dev/sdb1 9.0T 2.5T 6.6T 28% /srv/dev-disk-by-uuid-38b43865-79cd-44ed-ad35-40afa0c16f53
shm 63M 0 63M 0% /var/lib/containers/storage/overlay-containers/9b067d655f0dd35f1350aafb21c23185a1d62081da30d5ee7720a7db6238e064/userdata/shm
overlay 6.9G 6.5G 0 100% /var/lib/containers/storage/overlay/40b4c96e2d909e00ebdcf1f17369ba5f15ab0ce8c03602b21caad7aac1728ff4/merged
overlay 6.9G 6.5G 0 100% /var/lib/containers/storage/overlay/29e75ade8ddb45ad421e3c624f0ee7f5f266a56b2889b3ab191f89c961203848/merged
overlay 6.9G 6.5G 0 100% /var/lib/docker/overlay2/a23f24e1431274c4a39102810e016d48c9b3f94a138fb3784cc794a28f9b124d/merged
overlay 6.9G 6.5G 0 100% /var/lib/docker/overlay2/431c7464798fb7be555870391f65117b3414c7fe2575b6f7621dc16daec202b9/merged
overlay 6.9G 6.5G 0 100% /var/lib/docker/overlay2/7e914c9724dc1d4ce03716065ee3f14aa2ba31161723e8eac203c97a19f9f012/merged
As it is using overlay2 driver I assume it has something to do with those overlay lines that point to /var/lib/docker
If i run docker system df
I get
TYPE TOTAL ACTIVE SIZE RECLAIMABLE
Images 5 4 1.855GB 40.63MB (2%)
Containers 4 3 169.6MB 0B (0%)
Local Volumes 4 3 47.28MB 0B (0%)
Build Cache 0 0 0B 0B