Volume Configuration Not Persisted and Missing Apache Container in Nextcloud AIO on Synology DSM with Portainer

[laksjdf]

Support intro

Sorry to hear you’re facing problems.

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

• Official documentation (searchable and regularly updated)
• How to topics and FAQs
• Forum search

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can.

The Basics

• Nextcloud Server version (e.g., 29.x.x):
  • 11.7.0
• Operating system and version (e.g., Ubuntu 24.04):
  • Synology DSM 7.x
• Web server and version (e.g, Apache 2.4.25):
  • ?
• Reverse proxy and version _(e.g. nginx 1.27.2)
  • -
• PHP version (e.g, 8.3):
  • ?
• Is this the first time you’ve seen this error? (Yes / No):
  • yes
• When did this problem seem to first start?
  • Installation
• Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
  • AIO
• Are you using CloudfIare, mod_security, or similar? (Yes / No)
  • No

Summary of the issue you are facing:

I am experiencing issues with my Nextcloud AIO setup running on a Synology DSM system managed via Portainer. Below is my current docker-compose.yml configuration for the master container:

services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:latest
    init: true
    restart: always
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /volume2/docker/nextcloud/ncdata:/mnt/ncdata
    network_mode: bridge
    ports:
      - "8081:8080"
      - "11002:11000"
    environment:
      - APACHE_PORT=11000
      - APACHE_IP_BINDING=0.0.0.0
      - SKIP_DOMAIN_VALIDATION=true
volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

Issues:

1. Volume Configuration Not Persisted:

   • Upon initial start, the nextcloud-aio-nextcloud container fails to start because the directory configuration for ncdata does not match that defined in the compose file.
     Volumes (on initial creation) of nextcloud-aio-nextcloud:

     Host/volume	Path in container
     nextcloud_aio_nextcloud	/var/www/html
     /mnt/ncdata*	/mnt/ncdata

     *I’d expect /volume2/docker/nextcloud/ncdata here

   • When I manually change the volume configuration within the Nextcloud container to point to /volume2/docker/nextcloud/ncdata, it starts accordingly.
     It reverts back to the previous configuration (see table) upon container restart. This behavior disrupts the setup and prevents Nextcloud from accessing the correct data directory.

2. Missing Apache Container:

   • The expected Apache container (nextcloud-aio-apache) does not exist in my current setup. It seems that this container is required for the Nextcloud AIO configuration to work correctly. It simply isn’t there.

     

Could someone please assist with resolving these issues? Are there any specific configurations or steps I need to follow to ensure the volume settings persist and the Apache container is created and correctly linked?

Thank you for your help.

Steps to replicate it (hint: details matter!):

1. Deploy stack via compose (in portainer)

2. Create containers (without any optional containers → all boxes unchecked)

3. nextcloud container won’t start & apache containers isn’t there

Log entries

nextcloud-aio-mastercontainer log (issue 1.)

Message: Could not start container nextcloud-aio-nextcloud: {"message":"Bind mount failed: '/mnt/ncdata' does not exist"}

[szaimen]

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

[laksjdf]

Thanks! It works now! I knew I was missing a small thing.

Here’s my updated compose (might help someone else):

services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:latest
    init: true
    restart: always
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro

    network_mode: bridge
    ports:
      - "8081:8080"
      - "11002:11000"
    environment:
      - APACHE_PORT=11000
      - APACHE_IP_BINDING=0.0.0.0
      - SKIP_DOMAIN_VALIDATION=true
      - NEXTCLOUD_DATADIR=/volume2/docker/nextcloud/ncdata

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer