view the rest of the comments
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!
When I had Windows I ran WSL2 + standard Linux docker, worked flawlessly. If you have all your files in the WSL volume, it's also really fast compared to Docker Desktop on Windows or Mac. I found it almost as fast as a native Linux version.
This is what I do as well. I generally use it for testing then deploy it on my home server in a linux VM.
I thought WSL2 made things slow because of some stupidity they did with the code? Maybe they fixed it.
Anyways, is it able to take as much resources as it needs from the host? Unrestricted in terms of RAM and CPU?
It's slow when you go cross-filesystem, meaning accessing WSL2 files from Windows, or accessing Windows files from WSL2. If you keep all related files in WSL2, it's really comparable to native Linux experience (with a small penalty due to being ran in a VM, but it's not noticeable by a human eye).
As far as I know, yes, it can take all the resources it needs.
https://learn.microsoft.com/en-us/windows/wsl/wsl-config#configuration-setting-for-wslconfig
That’s probably referring to how file systems are handled. Going from WSL to windows file system is slower than using the “proper” mount point
yes
nice! Thanks! :)