this post was submitted on 12 Jun 2025
21 points (92.0% liked)

Selfhosted

46654 readers
1245 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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 are viewing a single comment's thread
view the rest of the comments
[–] MangoPenguin@lemmy.blahaj.zone 6 points 3 weeks ago* (last edited 3 weeks ago)

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/volumes