Question about changing data DIR? #890
-
|
Hi Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 28 replies
-
|
I guess the simplest way would be stopping all containers from the aio interface, creating a backup, use rsync to sync the files from the old datadir (in your case probably /var/lib/docker/volumes/nextcloud_aio_nextcloud_data/_data/ into e.g. /mnt/ncdata) and then removing and recreating the mastercontainer with Another solution would be stopping all containers from the aio interface, creating a backup, removing and recreating the mastercontainer with Hope it helps! |
Beta Was this translation helpful? Give feedback.
-
|
Hi - I tried this for moving the data dir and it comes up ok, but the Borg directory showing is still pointing to my original (custom) location. How can I amend the Borg archive location? I don't see any option to change it in the admin panel in the master container backup section. |
Beta Was this translation helpful? Give feedback.
-
|
Hi I want to use minio as my primary object storage with nextcloud aio . How to proceed |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Is it even possible to define in docker-compose.yml that it should use a different path for everything? Thank you for your support and feedback. |
Beta Was this translation helpful? Give feedback.
-
I'm looking to do the same, specifically for the nextcloud_aio_database container. As far as I'm concerned, this container contains important user data and should be treated as such, not stored alongside replicable data like nextcloud itself and apache binaries. I'd like all user data (including the database) to be on my RAID-1 filesystem, rather than in /var/lib/docker on my OS drive which has no redudancy. However, I'd much prefer not to move all docker containers, or even all nextcloud all-in-one containers. I only need to be able to move the ones containing important configuration and user data. @szaimen Is this a possibility? |
Beta Was this translation helpful? Give feedback.
-
|
Basically to remove it, first get the correct name or container id with this command: sudo docker ps -s Before all of this make sure all the containers are stopped and that there /mnt/ncdata is created on your local machine with correct permissions: All above are Ubuntu linux commands. |
Beta Was this translation helpful? Give feedback.
-
|
Uma maneira simples para fazer com que os dados dos usuários que estão configurados, por exemplo, para /mnt/ncdata sejam gravados em um /mnt/sdc1, que é um HD fora do container, é fazer um mount com bind. para automatizar isso, pode ser feito o mapeamento no /etc/fstab, mas antes temos que garantir que o hd de dados sempre estará montado em /mnt/sdc1, já que no boot pode ser montado em local diferente, ou até mesmo ter mais hds no seu computadoir, então vamos lá: Esse UUID é o importante. feche o arquivo e dê um boot que já vai montar tudo certinho Depois pode verificar com o comando lsblk que você verá que /mnt/ncdata e /mnt/sdc1 estão mapeados pro mesmo local. Tive que fazer isso porque na configuração no meu nexcloud, em não aparece a opção de armazenamento "local" e não descobri o porquê. |
Beta Was this translation helpful? Give feedback.
-
|
I have "succesfully" changed the datadir to an NFS mount on the host, and all of the features and app work fine except the AppStore. Any Idea what could have happended here? This is the log output from the nextcloud container: This is the log output i get when I us the sudo docker exec nextcloud-aio-nextcloud tail data/nextcloud.log command: |
Beta Was this translation helpful? Give feedback.
-
|
I have been attempting to change the data storage location on the host with no success. I have a NAS with a CIFS share that is mounted on the nextcloud server at I have completely reset my nextcloud instance (removed all nextcloud containers and volumes) and brought nextcloud back up with the following environment variables set in my compose.yaml file: When I bring up the initial AIO configuration, it states: and When I bring up all follow-on nextcloud containers, the I can't find any log entries that provide any indication of why the mountpoint isn't at My desired end result is that the nextcloud data (actual documents) is actually stored on the share provided by my NAS, not stored on the host system. I don't care that the configuration, apps, etc, are stored on the host. The host has somewhat limited space (<1TB) and I have several terabytes of documents that I want to have available through nextcloud. Any help would be appreciated...thanks in advance! |
Beta Was this translation helpful? Give feedback.
-
|
Hi.... My name is Mike salutation...
Ok , my apologies on the time frame, let me take a look at it and see if I
can apply a fix... or pin point the issue to your problem.
…On Sun, Jun 15, 2025, 5:53 PM nilber79 ***@***.***> wrote:
I have been attempting to change the data storage location on the host
with no success.
I have a NAS with a CIFS share that is mounted on the nextcloud server at
/mnt/nextcloud_data with permissions www-data:www-data.
I have completely reset my nextcloud instance (removed all nextcloud
containers and volumes) and brought nextcloud back up with the following
environment variables set in my compose.yaml file:
NEXTCLOUD_DATA_DIR: /mnt/nextcloud_data
NEXTCLOUD_MOUNT: /mnt/nextcloud_data/
When I bring up the initial AIO configuration, it states:
Nextcloud's datadir is getting stored in the nextcloud_aio_nextcloud_data Docker volume.
and
The Nextcloud container is getting access to the /mnt/nextcloud_data/ directory and local external storage in Nextcloud is enabled.
When I bring up all follow-on nextcloud containers, the
nextcloud-aio-nextcloud_data volume inspection shows that the mountpoint
is at /var/lib/docker/volumes/nextcloud_aio_nextcloud_data/_data.
I can't find any log entries that provide any indication of why the
mountpoint isn't at /mnt/nextcloud_data as specified by the environment
variables.
My desired end result is that the nextcloud data (actual documents) is
actually stored on the share provided by my NAS, not stored on the host
system. I don't care that the configuration, apps, etc, are stored on the
host. The host has somewhat limited space (<1TB) and I have several
terabytes of documents that I want to have available through nextcloud.
Any help would be appreciated...thanks in advance!
—
Reply to this email directly, view it on GitHub
<#890 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BH2IOA4QBJDLO3AGHIGXYOD3DXTL5AVCNFSM52YMJ2K2U5DIOJSWCZC7NNSXTOSENFZWG5LTONUW63SDN5WW2ZLOOQ5TCMZUG43DQNJT>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
I guess the simplest way would be stopping all containers from the aio interface, creating a backup, use rsync to sync the files from the old datadir (in your case probably /var/lib/docker/volumes/nextcloud_aio_nextcloud_data/_data/ into e.g. /mnt/ncdata) and then removing and recreating the mastercontainer with
-e NEXTCLOUD_DATADIR="/mnt/ncdata"and also starting the containers again from the aio interface.Another solution would be stopping all containers from the aio interface, creating a backup, removing and recreating the mastercontainer with
-e NEXTCLOUD_DATADIR="/mnt/ncdata"then restore the most recent backup and afterwards starting the containers again from the aio interface. In …