• 1 Post
  • 414 Comments
Joined 2 years ago
cake
Cake day: June 19th, 2023

help-circle

  • I run debian on everything, so I set up unattended-upgrades for security updates and basically forget about it. Docker updates are also automatic with Komodo, just make sure databases are pinned to a major version.

    For monitoring my services I use Uptime Kuma, and get an alert if a service goes down so I can fix it.

    Been pretty solid for years now. Things get rebooted every month or two when I do a Proxmox upgrade and reboot the host.



  • Install Debian as a server with no GUI, install docker on it and start playing around.

    You can use Komodo or Portainer if you want a webUI to manage containers easily.

    If you put any important data on it, set up backups first, follow the 3-2-1 rule by having at least 2 backups in place.

    The problem with stuff like yunohost is when it breaks you have no idea how to fix it, because it hides everything in the background.









  • Migration should be as simple as importing the existing ZFS stuff into the Proxmox OS. Having backups of important data is critical though.

    If I understand correctly, you can specify directories that live on the Proxmox Host, and they appear inside the VM, right?

    Inside a Container, yep. VMs can’t do bind mounts, and would need to use NFS to share existing data from the host to inside the VM.

    How does this compare to using virtual storage?

    Like a VM virtual disk? Those are exclusive to each VM and can’t be shared, so if you want multiple VMs to access the same data then NFS would be needed.

    But containers with bind mounts don’t have that limitation and multiple containers can access the same data (such as media).

    Also, how can I replicate the ZFS pools to an external machine?

    ZFS replication would do that.