Nextcloud AIO v15.1.1 volume paths changed

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

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:

(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).

When updating to v15.1.1 the volume paths were changed by the update routine and broke them. this is after in docker:

I can no longer start nextcloud - is there any way to fix this. Sorry I am newish to this and still finding my feet - so be gentle please

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 35.0.3.2
  • Operating system and version (e.g., Ubuntu 24.04):
    • docker
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • After update using nextcloud AIO
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO

Summary of the issue you are facing:

After the update this error appears:

error while creating mount source path ‘/host_mnt/Volumes/cloud’: mkdir /host_mnt/Volumes/cloud: permission denied

There are no folders it changed it from the predefined paths

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

last logs are before the update - when it worked

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

cant run

Hi @paul.newns, welcome! Don’t worry, this can be fixed, and your data is most likely still safe on your drive.

What the error means

The path /host_mnt/Volumes/cloud wasn’t set by AIO. Docker Desktop for Mac adds /host_mnt internally in front of folders from your Mac. So the folder in question is /Volumes/cloud on your Mac, which is probably the external drive you set as NEXTCLOUD_DATADIR or NEXTCLOUD_MOUNT.

permission denied while running mkdir means Docker can’t reach that drive. It tries to create the folder because it can’t see it. Usually the cause is outside AIO, for example:

  1. The drive isn’t mounted, or was mounted after Docker started. Make sure the drive named cloud appears in Finder. Then fully quit and restart Docker Desktop.
  2. Docker Desktop has lost access to the drive. This often happens after a Docker Desktop or macOS update.
    • Docker Desktop → Settings → Resources → File sharing: make sure /Volumes or /Volumes/cloud is listed. Add it if not, then click Apply & restart.
    • macOS System Settings → Privacy & Security → Files and Folders (and/or Full Disk Access): make sure Docker is allowed to access Removable Volumes.
  3. The drive’s name changed. If macOS mounts it as /Volumes/cloud 1 or similar, for example because a leftover empty /Volumes/cloud folder exists, the path won’t match anymore. In Terminal, run ls /Volumes and check that the name is exactly cloud.

Once Docker can see the drive again, open the AIO interface and click Start containers. It should work as before.

If it still fails

Please post the docker run command (or compose file) you used to start the mastercontainer, minus any secrets. Please also say whether you use Docker Desktop or something else, and your macOS version. That lets us check whether the datadir or mount setting matches your drive.

Also, as a tip for later: on macOS, OrbStack is often less trouble than Docker Desktop with external drives (see the macOS section in the AIO readme).


Disclaimer: This reply was AI-generated and reviewed before posting. Please double-check the steps for your setup.

Thanks - that pointed me in the right direction - The cloud drive had been renamed by the mac in cloud-1. When i unmounted it and cleared the ghost and remounted it worked - thanks again for your help