NextCloud AIO not starting after update to AIO 8.1 (/mnt/nextcloud is mounted on /mnt/nextcloud but it is not a shared mount)

🚧 Installation
, ,
1

Hi,

I’m currently testing NextCloud. After having applied the first update (AIO 8.0 to AIO 8.1) the Containers

  • Apache
  • Nextcloud
  • Notify Push

don’t start anymore,
Docker Socket Proxy remain on status “starting”, seeming to infinitely loop wit message “Waiting for Nextcloud to start… nc: bad address ‘nextcloud-aio-nextcloud’”

Before applying the updat nextcloud was up an running.

I can see error messages in the log, but I don’t have any clue how to continue:

Trying to fix docker.sock permissions internally...
Adding internal www-data to group ping
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No cpu shares support
e[0;92mInitial 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
⚠️ 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:8443e[0m
[10-Apr-2024 08:29:40] NOTICE: fpm is running, pid 134
[10-Apr-2024 08:29:40] NOTICE: ready to handle connections
[Wed Apr 10 08:29:40.703838 2024] [mpm_event:notice] [pid 125:tid 139627213474568] AH00489: Apache/2.4.58 (Unix) OpenSSL/3.1.4 configured -- resuming normal operations
[Wed Apr 10 08:29:40.704153 2024] [core:notice] [pid 125:tid 139627213474568] AH00094: Command line: 'httpd -D FOREGROUND'
{"level":"info","ts":1712737780.712568,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""}
NOTICE: PHP message: Slim Application Error
Type: Exception
Code: 0
Message: Could not start container nextcloud-aio-nextcloud: Server error: `POST http://localhost/v1.41/containers/nextcloud-aio-nextcloud/start` resulted in a `500 Internal Server Error` response:
{"message":"path /mnt/nextcloud is mounted on /mnt/nextcloud but it is not a shared mount"}
File: /var/www/docker-aio/php/src/Docker/DockerActionManager.php

The log has some more entries, please let me know if they might be of any help.

AIO is running on Docker on a LXD-Container on a QNAP NAS (TS-364 with 32gig RAM)

/mnt/nextcloud is mounted via QNAPs Container station. mount -l shows

/dev/mapper/cachedev1 on /mnt/nextcloud type ext4 (rw,relatime,stripe=256,data=ordered,data_err=abort,jqfmt=vfsv1,usrjquota=aquota.user)

Any help appreciated.
TIA
Michael

2

Since the mount point /mnt/nextcloud is not necessary for my nextcloud setup (I change from external mounted strorage to mount the externale files via a smb mount, I tried to remove the mount point:

  • downed the master container
  • stopped the LXD container
  • removed /mnt/nextcloud via QNAP’s “Container Station”
  • removed the env NEXTCLOUD_MOUNT from the master container
  • removed the AIO master container from docker
  • launched a new AIO master container

and now I get this error:

path /mnt/nextcloud is mounted on / but it is not a shared mount