If that were all this was, sure. In your analogy though, Google owns 95% of the grocery stores and has deals with 90% of the food vendors that if they allow you to stock their brands they lose access to sell in the Google grocery store. That practice is anticompetitive, because it functionally prevents you from opening your own store to compete.
Glad to hear. If there’s a lesson to be taken from here, it’s to make sure after installing a distro, make note of anything odd in dmesg, journalctl, etc. There’s about eight rabbitholes you could have gone down for weeks and overlooked the obvious here just because we didn’t know what “normal” looked like for your system.
/drive is not a standard mount in a Debian install. Presumably that’s something you did.
There’s also no unaccounted for partitions on /sda
If you comment that like out for the /drive mount, it should boot. I’d say better than 50/50 the rest of that is red herrings that have been there since you installed
If someone had some theoretical device that could x-ray, 3d image, and 3d print an exact replica of your car though, that would be legal. That’s a closer analogy.
It’s not illegal to reverse-engineer and reproduce for personal use. It is questionably legal though to sell the reproduction. However, if the car were open-source or otherwise not copyrighted/patented it probably would be legal to sell the reproduction.
What would it cost to retrieve though? You probably still have the appropriate cost-effective solution but it’s an important consideration for newcomers to have complete math.
You aren’t wrong, but his question seemed genuine. There’s no reason to be hostile about it. Learning and genuine curiosity shouldn’t be a crime on the Internet.
Apparmor will complain and block the nfs mount unless you disable apparmor for the container. Then in a lot of cases the container won’t be able to stop itself properly. At least that was my experience.
Proxmox uses scsi for disk images, which are single access only
Smb would be quite a lot of overhead, and it doesn’t natively support linux filesystem permissions. You’ll also run into issues with any older programs that rely on file locks to operate. nfs would be a much more appropriate choice. That said, apparmor in container images will usually prevent you from mounting remote nfs shares without jumping through hoops (that are in your way for a reason). You’ll be limited to doing that with virtual machines only, no openvz/containerd.
Fun fact, it was literally the problems of sharing media storage between multiple workflows that got me to stop using virtual machines in proxmox and start building custom docker containers instead.