#3
this post was submitted on 28 Jan 2026
27 points (100.0% liked)
Selfhosted
55801 readers
501 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: 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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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 2 years ago
MODERATORS
Interesting. Could you expound on why that option, and what some pros and cons would be?
The simplest and most pragmatic option.
thank you sir
Hosting things in docker separates then from the OS and makes upgrading safer and easier.
Eventually, you'll want to update your OS. If the software is right on the OS, you might break it. If it's in docker and the machine breaks, run the container on another machine.
If you upgrade your software and it breaks, in docker you just go back to the previous container. It's still there and hasn't changed. If the software is on your OS directly, an uninstall and reinstall might work, but might not.
It depends what your long term goals are. If it's just to run those services as simply as possible, then just run them in docker on windows. If you want to learn Linux, then setup you other hardware and install a server distro. Ubuntu is fine, but I use Debian.
Then once you get used to Linux, one day you could migrate your Plex server to Linux and remove windows from your main server.
Why run a docker through a vm on Windows when you can just run docker natively? I don’t understand the convolution.
Use whatever you are more comfortable with.
Thats how docker runs "natively" on windows, its kernel has no support for namespaces nor cgroups that containers require
WSL, Hyper-V and Windows Containers are all options
they have to be built specifically for windows (of course the kernels are different, so the binaries are going to be different) but you can run Windows native applications on Windows kernel with a different implementation of containers using the standard Docker CLI and interfaces
Cgroups are just 1 (by far the most common) implementation of the container backend
Mind linking the relavent simplex SMP/xftp windows container then?
i’ve already linked the docs that state that native windows containers exist. whether or not specific images exist is not relevant
No. You can install docker directly in Windows. OP is running a Linux VM and then docker inside of that.
Docker desktop for Windows runs under WSL or Hyper-V, both being VMs themselves.
Arguably running a Linux VM themselves will only offer them more customisation options (although may be heavier than WSL)
Yunohost
Question: what are the advantages of simplex over signal?
Not centralized, no phone numbers needed
But if you host a server then your contact should configure that server to communicate with you?
Nevermind it's a swarm of servers.