They’ll make whatever sells subscriptions at this point.

Don’t buy, only subscribe. From media to software and now to hardware and OS. No more license keys you can reuse, no more owning what you pay for, just live services and ever-rising subscription costs that can change at any time for any reason and neuters your ability to take legal action against them while they do it.

Silence critics, control available options, capture profit - that’s the name of the game. They’ll sell this to businesses as ‘take your PC anywhere’ like you couldn’t already do that and then they have a hunk of plastic and silicon they need to pay out the nose for until they finally give it up. And they’ll have to give it up because it literally can’t run anything else on the available hardware. I’m sure folks will hack it apart but like, what’s the point?

Speaking of where we’re talking on just now, Lemmy support in general would be great too. Not sure but I assume your suggestion would mean the same thing?

So CosmOS does run through Compose files, but it makes them on the fly and gives you a moment before runtime to review it and make any changes.

Am I understanding right that your idea here is to put the Volumes on the NFS share and run through that, as opposed to having the data outside of a Volume just sitting on an NFS Mount?

I’m still early enough in that if something’s wrong or not ideal about the config, I can go scorched earth and have the whole thing back up and running in an hour or two.

Is there a better filesystem that I could share out for this kind of thing? My RAID Array is run through OpenMediaVault if that helps.

That tracks with my experience as well. I’ve been trying to get a system set up where the OS and Docker live on a small disk by themselves, and then go out to the larger RAID Array to load its data. But it’s sounding like that’s not really going to work the way I want to (probably why it’s crashed on me so many times, too).

So I have a 2TB nVME for VM Host Disks, and a 72TB RAID Array on my server. My hope is to have the OS and Docker on the 32GB drive I set up for the VM (which lives on the nVME), and then all the files related to the webapps live in a folder on RAID Array in a section meant just for that.

But the other responses in this thread make me think that’s not really going to be an option. Maybe I could make a very large VM Host Disk and put it on the RAID Array, let Docker just forget about the mount points entirely…

You want to advertise to me in the OS? Don’t charge me $200 for the OS then!!

What kind of therapy do I go to if I’m in an abusive relationship with my Operating System?

🎶Good times never skies so blue🎵

I realize I’m preaching to the choir on here, but really has never been a better time to learn Linux

I was really just using SMB for convenience sake, one less protocol for me to turn on and configure. I initially thought about NFS but when I realized how little I know about actually securing NFS I decided against it. Though, I suppose that’s led me to this point here.

Trying it stock is exactly what I was thinking, though what folks have said about NixOS makes me think that’s going to be the first thing I try.

Very first experience was NC-Pi, right before that project got canned. Loved it so much I spent a couple hundred on shared hosting and set v24 up there, but I’ve been trying to move to my homelab because A) One less bill B) I can use the 72TB RAID Array for storage instead of the 30GB storage I paid way too much for.

Honestly have had great experiences with Portainer so far, with Nextcloud being the only real exception. PiHole, Dashy, an introducer for Syncthing, and StashApp all run without a hitch via Compose files dropped into Portainer. Though I am definitely going to take Docker out of the picture for the next NC install which means taking Portainer out as well.

I’ve only ever used the official repositories, basically followed the install documentation to get the letter. I do management of it through Portainer but that’s just a convenience for testing. Once I got the Compose file just right I’d docker up -d inside the folder on the VMs main drive.

The actual files were saved to a mounted SMB share, and I’m not sure if it’s related or not but I also had a media folder mounted as SMB and configured to be shared as External Storage within Nextcloud itself. I keep wondering if the database isn’t killing itself trying to read everything in there…

Trying not to learn another deployment scheme, but keeping this on the list. Thank you for sharing!