this post was submitted on 16 May 2026
22 points (95.8% liked)
Selfhosted
60451 readers
538 users here now
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
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!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you are running a non home version of Windows you could install the Hyper-V services on your computer and start with VMs that way.
Another option is VMware Workstation/Fusion now that it is free again, or Virtual Box by Oracle.
That is what I did for a while. A Debian VM with 2 CPUs MD 8Gb of ram to start playing around with Docker before getting a Pi.
You don't mention where you are from so apart from eBay there isn't really much else to go with.
Oh, it is again? Thanks for letting me know!
Will try this out, then, thank you for the advice! Since I got my PC on ethernet, but still got a network card with WiFi that I don't really use for anything, I could set it up so the Wifi card acts as part of the VM as a different computer in the network, instead of having to configure the same connection both for my PC and the VM, right?
You don't need to use a dedicated card for networking, assuming you have a PC from the last decade the hardware is smart enough to share the NIC.
I bridge my ethernet NIC between Windows and my Hyper-V VMs and everything talks just fine.
He'd be better off with a bare metal implementation like Proxmox.
Hyper V is bare metal. Hyper V is a type one hypervisor. The hyper v kernel runs under the windows kernel, when you run hyper v, the windoss you interact with is transparently converted into a VM, with all devices passed through to it.
Anyway the tools to manage hyper v aren't anywhere near as mature compared to proxmox and it's a pain when you hit corner cases so I wouldn't recommend it, BUT it is a type 1, highly performant hypervisor.