Selfhosted

40246 readers

789 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Data storage for containers in LCX / VM (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by conrad82@lemmy.world to c/selfhosted@lemmy.world

13 comments fedilink hide all child comments

I run my containers in an LCX on Proxmox (yes I heard I should use a VM, but it works..)

For data storage (syncthing, jellyfin ..) I make volumes in the LXC. But I was wondering if this is the best way?

I started thinking about restoring backups. The docker backups can get quite large with all the user data. I was wondering if a separate "NAS" VM and NFS shares makes more sense. Then restoring/cloning docker lxc would be faster, for troubleshooting. And the user data I could restore separately.

What do you guys do?

you are viewing a single comment's thread
view the rest of the comments

[–] pqdinfo@lemmy.world 2 points 1 year ago (1 children)

I'm not directly familiar with either, but syncthing seems to be about backing up, so I'm not entirely surprised it's file oriented, and jellyfin doesn't look like it's about user maintained content so much as being a server of content. So I'm not entirely surprised neither would support S3/Minio.

Yeah it took me a while to realize what S3 is intended to be too. But you'll find "Blob storage" now a major part of most cloud providers, whether they support the S3 protocol (which is Amazon's) or their own, and it's to be used precisely the way we're talking about: user data. Things clicked for me when I was reading the DoveCot manuals and found S3 was supported as a first class back-end storage system like maildir.

I'm old though, I'm used to this kind of thing being done (badly) by NFS et al...

[–] conrad82@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

Huh. I recently set up local dovecot for archiving old emails, but not S3.

I'm curious, when you work on a document, how does that work; Is it a file on your hard drive, have you mounted a bucket somehow, do you sync using restful api somehow?