The usual go to for self hosted password managers is VaultWarden. There’s no deb or rpm package but you can get it spun up with docker pretty easily. Any reason you’re specifically looking for “included” or packaged solutions? That’s going to severely limit your options.
I run a supermicro chassis with 6 3TB drives in a RAID6 using a dedicated hardware RAID controller. Old school for these days but works for my needs for now. Drives were free from a buddy of mine so until they start dying or I need more space, they’ll do. Then I have two 120GB intel enterprise SSDs for running Proxmox. VMs and LXCs are all on the spinning disks which surprisingly perform well enough.
I run a supermicro chassis with 6 3TB drives in a RAID6 using a dedicated hardware RAID controller. Old school for these days but works for my needs for now. Drives were free from a buddy of mine so until they start dying or I need more space, they’ll do. Then I have two 120GB intel enterprise SSDs for running Proxmox. VMs and LXCs are all on the spinning disks which surprisingly perform well enough.
I run a supermicro chassis with 6 3TB drives in a RAID6 using a dedicated hardware RAID controller. Old school for these days but works for my needs for now. Drives were free from a buddy of mine so until they start dying or I need more space, they’ll do. Then I have two 120GB intel enterprise SSDs for running Proxmox. VMs and LXCs are all on the spinning disks which surprisingly perform well enough.
There’s a bit to explain here. So the root user is basically the equivalent of Administrator. One big difference (there are many) is that when you run something as root using sudo, you are actually running as the root user. When you ran the first command to create the folder, you created it in your home directory using the ~ shorthand variable which points to your /home/ user folder. The second command, also references your home folder. However since your running as root, it’s looking for the file in the root user’s home directory or /root, not your home folder.
The config file needs to be in the home directory of the user running the command unless you can put the full path to the config file in the command, then you can put it wherever you want.
Not weird at all. All my data is shared from a single VM but I access it from several others than run jellyfin and the *arrs, and a few other things. When you don’t want everything running on the same virtual machine, you need to share the data over the network, even if it’s all on the same physical box.
If you want multiple containers or VMs to have access to the data it needs to be shared from somewhere. As others have mentioned you can setup a VM to run a NAS OS like FreeNAS or just run a container with samba and pass the drive through to the container. The difference is how you access the data from the other containers and VMs. You’ll access them via samba shares as opposed to local drives.
To my knowledge two containers/VMs cannot share the same physical or virtual disks in Proxmox. I tried and had to go a different route to get what I needed.
Everything else just makes it easier to manage which depending on your preferences and how much content you’re dealing with that may not be a problem for you. I run the whole stack using Deluge as my downloader with a VPN. Radarr, Sonarr, and Lidarr automatically locate the torrents on the public tracker sites for me, send the downloads to Deluge, and imports the media into Jellyfin when the download finishes. I also use Jellyseer for discovering and requesting content, as well as allowing family members to request content. I also use Prowlarr to manage the trackers being used in the various arr apps. It’s a very robust and automated system but it all boils down to just downloading torrents over a VPN.