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?

  • VelociCatTurd@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    11 months 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.

  • Fermiverse@kbin.social
    link
    fedilink
    arrow-up
    3
    ·
    11 months ago

    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.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      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
        link
        fedilink
        arrow-up
        1
        ·
        11 months 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.

  • TCB13@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    11 months ago

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

    • conrad82@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      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
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        11 months 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.

    • conrad82@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      Interesting! I felt S3 was more a business cloud storage api.

      I did a quick search, and it seems neither syncthing or jellyfin is compatible with S3. What do you do in these cases?

        • conrad82@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          11 months 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?

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    11 months 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]