Little bit of everything!

Avid Swiftie (come join us at [email protected] )

Gaming (Mass Effect, Witcher, and too much Satisfactory)

Sci-fi

I live for 90s TV sitcoms

  • 21 Posts
  • 895 Comments
Joined 2 years ago
cake
Cake day: June 2nd, 2023

help-circle

  • I really wanted it to work, for me it made the most sense I thought, as little virtualization as I could do. VM felt like such a heavy layer in between - but it just wasn’t meant to work that way. You have to essentially run your LXC as root, meaning that it’s essentially just the host anyway so it can run docker. Then when you get down to it, you’ve lost all the benefits of the LXC vs just running docker. Not to mention that anytime there was even am minor update to proxmox something usually broke.

    I’m surprised Proxmox hasn’t added straight-up support for containers, either by docker, podman, or even just containerd directly. But, we aren’t it’s target audience either.

    I’m glad you can take my years of struggling to find a way to get it to work well and learn from it.



  • Not at all. Proxmox does a great job at hosting VMs and giving a control plane for them - but it does not do containers well. LXCs are a thing, and it hosts those - but never try to do docker in an LXC. (I tried so many different ways and guides and there were just too many caveats, and you end up always essentially giving root access to your containers, so it’s not great anyway). I’d like to see proxmox offer some sort of docker-first approach will it will manage volumes at the proxmox level, but they don’t seem concerned with that, and honestly if you’re doing that then you’re nearing kubernetes anyway.

    Which is what I ended up doing - k3s on proxmox VMs. Proxmox handles the instances themselves, spins up a VM on each host to run k3s, and then I run k3s from within there. Same paradigm as the major cloud providers. GKE, AKS, and EKS all run k8s within a VM on their existing compute stack, so this fits right in.



  • I think at this point I agree with the other commenter. If you’re strapped for storage it’s time to leave Synology behind, but it sounds more like it’s time to separate your app server from your storage server.

    I use proxmox, and it was my primary when I got started with the same thing. I recommend build out storage in proxmox directly, that will be for VM images and container volumes. Then utilize regular backups to your Synology box. That way you have hot storage for drives and running things, cold storage for backups.

    Then, inside your vms and containers you can mount things like media and other items from your Synology.

    For you, I would recommend proxmox, then on top of that a big VM for running docker containers. In that VM you have all of your mounts from Synology into that VM, like Jellyfin stuff, and you pass those mounts into docker.

    If you ever find yourself needing to stretch beyond the one box, then you can think about kubernetes or something, but I think that would be a good jump for now.










  • They ran off even their most loyal players one by one with their asinine moves. Lame games, vendor lockin, nickle and dining.

    I was die hard for Xbox. Had every one, dozens of games, more probably. Have fond memories of lan parties and friends coming over to play split screen. I remember playing through halo 3 the night it dropped into the early morning, and getting the beta from Reach.

    Then they killed off split screen. And lan gaming. You had to use Xbox live to play with your friend in the room. Oh no they don’t have Xbox live. Oh no there’s an update. Now they don’t have their password. They can’t join my party. The audio doesn’t work. It became a hassle to play with people

    Steam just works. And it’s a fair price




  • There’s many ways to do this. Saving the disk state is one, I believe that’s what the other person suggested - essentially stores the disk as an image which then you use for future vms as your jumping off point. This is also essentially how workstations are deployed at companies. (Essentially being the key word). Cloud providers have different names for this too, in AWS this is called their AMI.

    Another option is Ansible, which essentially handles deploying a VM by running your scripts for you. I haven’t played too much with this, and I doubt it works with VirtualBox, but it’s something you may want to look into, it would definitely uplevel your skills.

    Thirdly is dependent on what you actually use your VM for, you haven’t given your use cases but this is one of the reasons containerization became such a thing - because when running an app we mostly don’t care about the underlying system. It may be worth it to learn about docker.