this post was submitted on 17 Aug 2023
9 points (90.9% liked)

Selfhosted

61129 readers
369 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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?

all 13 comments
sorted by: hot top controversial new old
[–] VelociCatTurd@lemmy.world 4 points 3 years ago

I run my dockers all in one VM, with persistent volumes over NFS. That way the entire thing could take a dump and as long as I have the nfs volume, we’re Gucci.

[–] TCB13@lemmy.world 3 points 3 years ago (1 children)

If you're using LXC and your filesystem is BTRFS you can use the built in snapshots.

[–] conrad82@lemmy.world 1 points 3 years ago (1 children)

Yes, before doing major changes i usually run a snapshot

I listened to https://thehomelab.show/ podcast today, and they mentioned that before doing major upgrades, you could create a clone VM from latest backups and test the upgrades before doing them for real. That way you both ensure safe upgrade and also make sure your backup is restorable.

It sounded like a good idea, but it got me thinking of the size of my LXC filled with user data.. So I was wondering if I was doing it wrong

[–] TCB13@lemmy.world 1 points 3 years ago* (last edited 3 years ago)

With BTRFS you can take a snapshot, upgrade and if things go wrong rollback to the snapshot. Snapshot are incremental so you won't have issues with your data.

[–] Fermiverse@kbin.social 3 points 3 years ago (1 children)

I use unpriveliged LXC für everything I have running in my proxmox.

Plex, syncthing, rclone, motioneye, pyload all in seperate Lxc on the boot drive.

All data of those is on my mirror raid, including the lxc backups. The rclone lxc backs the important data onto my cloud drive.

[–] conrad82@lemmy.world 1 points 3 years ago (1 children)

Do you use reverse proxy?

One of the reasons I use a single lxc is that I can reverse proxy containers without exposing ports / http to the LAN, it seemed like a good feature to me.

[–] Fermiverse@kbin.social 1 points 3 years ago

No reverse proxy. In LAN everything is seen and accessible.

No port is open to WAN, I connect via my router VPN from extern.

[–] Decronym@lemmy.decronym.xyz 2 points 3 years ago* (last edited 3 years ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
LXC Linux Containers
Plex Brand of media server package
VPN Virtual Private Network

3 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.

[Thread #57 for this sub, first seen 17th Aug 2023, 17:45] [FAQ] [Full list] [Contact] [Source code]