Yeah, actually I had that setup for a brief amount of time, but I had issues because my system has too little RAM, and TrueNAS and Docker were constantly fighting over RAM, and the system hang frequently. For some mindboggling reason, if I ran TrueNAS and a Docker VM separately on Proxmox, were I could manually specify allowed RAM, everything worked perfectly fine, even though the available RAM was still very low. If I ever go down this road again, I’ll need to buy more RAM sticks.

You’re right, I misunderstood. I understand now, thank you for replying with detail. I’m currently still not over my “I like Hypervisors now” phase. If I go back to bare metal, I will most probably use the setup you described. Still, thank you very much, and I’m keeping this thread for future reference.

Wow, that’s awesome. I think that’s actually the approach I’m going to go for. This way I don’t need to buy hardware, and I don’t need to work with TrueNAS anymore.

Where you talk about “walking the backups”, do you mean that you can actually see the entire file structure of the container? I mean, I don’t know how virtual disks are stored on the dataset. Like, as far as I know, a VM virtualized disk is just a file, right? So you’d have a ZFS dataset with a single file, for example? Could you then try and navigate the files inside this VM disk file, without the VM? Or did I misunderstand, and you’re mounting the dataset, somehow, directly inside the VM? Is that like a passthrough for datasets?

In any case, thank you for sharing so much information and for offering help. I may take you up on that, as it seems that this is the approach that I feel most comfortable with.

Okay, thank you, that’s good to know. However, I don’t have two separate devices that I can use to separate the NAS functionality from the Docker functionality, that’s why I was using Proxmox in the first place. And, I’m not sure how well Docker can run in OMV. But I’ll still keep it in mind as an option, thank you!

I tried OMV in the past, but I found TrueNAS to be more intuitive… but that’s just personal preference I guess, and I’m not opposed to using OMV. Are you suggesting, then, that I run OMV on bare metal, and use it for everything? Or should it be inside a VM? If it’s the former, how easy is it to setup docker, because I’m not that familiar with OMV (it’s been a long time since I last checked it out). Is it like installing it in Debian directly? How does it handle the storage?

Wait, so if I understood correctly, you’re managing the ZFS pools directly in Proxmox, and then you have a VM that’s running docker, and using the storage that is managed by Proxmox, right? Hmm, sounds like a good solution. Is there any documentation or article that you could recommend, so that I can take a closer look? Also, how could I handle SMB shares?

Correct, they’re two separate pools, and the stripe one doesn’t contain any valuable data.

Thank you, I might raise the issue there, if I struggle to fix the issue. I didn’t know the podcasters, but now I’ll try and listen to a few episodes, and maybe I can continue learning. Thank you for the suggestion

And is it easy for the docker instances inside the VM to access the host’s datasets? About ECC, thank you for bringing it up, because I actually have no idea on the subject, and I’m sure that my current ram isn’t ECC. I’ll look into it. It could explain the issue I had with gitea, right?