So I currently have a 1tb drive running all of my containers for my home server. I’m trying to finalize the process of transitioning from corporate cloud storage to my own personal cloud. I have a new 12 TB drive to hold all my files.
I am running Xubuntu, with OwnCloud running in docker compose similar to this setup.
By default, it saves all data in the var directory, but I am stuck with how to change it. I have my data backed up separately, so the plan is to set it up from scratch.
There are complicated instructions here, but I don’t have the skill to transfer this process to a docker compose installation. I have never used SQL commands, and I really have no idea how to do anything with it in docker.
This is a critical step in my home server setup, without which I pretty much can’t move forward. Can anyone help?
Edit: Thanks from a real beginner. I was making it harder than I needed. The default volumes in the YML file were in an unfamiliar format to me. I rewrote the relevant lines and re-initialized and now it is working as intended.
I guess I am still learning about the different ways that volumes can be designated in yaml.
You must log in or register to comment.
Since you’re running it in docker all you need to do is change the mount locations in your docker-compose file. Then copy the existing data to the new location.
If you’re currently using a volume instead of a bind mount then the existing data will be under
/var/lib/docker/volumesApart from changing the docker config of your existing installation you can also symlink the new folder to the old location.
Or if Docker or Nextcloud doesn’t like symlinks you can also mount the folder there. Folders can be mounted more or less the same as devices.
I’m not quite sure what you’re trying to do here. Are you
- Trying to create a new owncloud instance and put your data somewhere other than in /var, or
- Try to move the data location of an existing owncloud instance?
If you’re trying to do the second one, there’s a useful guide on it here: https://omiid.me/notebook/25/move-docker-volume-to-bind-mount. The first one should be even simpler, you can just replace the volumes in the compose file by bind mounts (basically, just this step of the tutorial: https://omiid.me/notebook/25/move-docker-volume-to-bind-mount#modifying-docker-compose).
If you’re doing a fresh instance it will solve a lot of issues. Personally I run a Nextcloud instance which got its own 2TB SSD. I mounted the disk at /nextcloud, then used bind mounts in docker compose for db and NC.
