-
Is your feature request related to a problem? Please describe.For those of us who are still learning how to parse docker commands, the instructions in the migration.md document are a little hard to follow, specifically in step 6. Having mapped the NEXTCLOUD_DATADIR to /mnt/tank/nextcloud_data/ in the compose file, I have a hard time knowing how to adjust the chown/chmod commands in step 6. I have a working installation, but when I stop all the containers to run those commands in step 6 (which I'm probably doing wrong?), I get failures, and the nextcloud-aio-nextcloud container fails to fully start. Describe the solution you'd likeThe other steps have clear instructions for exactly where and how to enter /path/to/nexcloud/data/ and I think this would be helpful for step 6 as well. I realize that in step 5, the path being referenced is the location of the existing/old nextcloud data, and in step 6, the path being referred to is the new location for the AIO instance. Perhaps something like /path/to/old/nextcloud/data/ and /path/to/new/nextcloud/data/ to keep the distinction? Describe alternatives you've consideredAdditional contextI can provide more info on specific errors, but I'm pretty sure this is the part I'm doing wrong. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
It seems like no matter how I enter the commands, I always end up with this error in the logs of the nextcloud-aio-nextcloud container:
I don't mean for this to be asking for specific help in the wrong place, but there seems to be a real deficiency in the documentation on this point. |
Beta Was this translation helpful? Give feedback.
-
Hi, thanks for the idea! This was done in 99c5ae8 |
Beta Was this translation helpful? Give feedback.
-
As for your other issue, you need to follow this:
|
Beta Was this translation helpful? Give feedback.
As for your other issue, you need to follow this: