Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
A VPS is already a VM and nesting VMs, even if you get it to work, is generally a Bad Idea™️.
What you're asking for is squarely in "bare metal" territory. Does that reduce your flexibility? Sure. But it doesn't entirely eliminate it. Down the road if you decide you need more RAM or disk those are things you can have added (at a cost). CPU would likely necessitate a migration to a different system so I'd keep that in mind during initial sizing. Also, if you are using proxmox, migration will be as simple as backing up a container/VM and restoring it at the destination.
Your other alternative is multiple VPSes or possibly augmenting the bare metal server with one or more VPSes.
As far as unified billing goes, just have all the services with the same provider. Most providers I've encountered offer both services.
I can't speak to providers in our around Sydney, but I'd recommend checking out lowendbox.com to start your search.
Thanks. As bare metal is quite a bit more expensive, what would I lose by going to a VPS? I'm assuming Proxmox and Windows, assuming I wanted to go with a Linux VPS. Would there be issues with running Docker containers with the VPS?
With a vps expect to lose all virtualization
Is Docker considered virtualisation?
Docker requires hardware virtualization so kinda but not really. Apparently it runs inside of a VM so that's a no go.
Honestly I think you're asking way too much for a VPS, or even a full blown server. If you want to run CAD software you'll also want a remotely capable GPU and you won't get that in a server unless you've explicitly put something in it. The built in GPUs in servers are like radeon 3450s that are 15 years old and are basically just video adapters and not actual "graphics processing units". If you have your own server I'd throw a GPU in there and try running your software there. But honestly any remotely modern laptop will probably run faster than a cheap rented server.
No docker is not virtualisation, the poster below is talking about docker for desktop which is a nice gui wrapper around it in a VM, but by definition docke itself does not use any form of virtualisation. If you had a modern Linux server you can install any of the container runtimes, e.g. docker, podman to run containers or something like K3S which is effectively a lightweight kubernetes if you wanted to run a lot of different containers and have a central way of managing them
I run docker exclusively in VMs and VPS and it works fine.
It's already all virtualized, so from customer perspective, advantages of virtualization aren't there (single box, maximizing use of local resources, etc).
Wouldn't you be able to do containers in a Linux VPS though? To the host, it's just a virtualized Linux, from Linux' perspective, those containers are local resources.
Looks like you'd still need virtualization.
Docker desktop is not what most people on Linux are using. They're using docker engine directly, which doesn't run in a vm, and doesn't require virtualization if you use the same kernel inside the containers.