Selfhosted

60623 readers

2128 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:

Detailed Rules Post

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. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Replacement for Docker Desktop on Windows? (lemmy.world)

submitted 2 years ago by damnthefilibuster@lemmy.world to c/selfhosted@lemmy.world

35 comments fedilink hide all child comments

Folks, I have a node.js script running on my Windows machine that uses the dockerode npm package to talk to docker on said box and starts and kills docker containers.

However, after the containers have been killed off, docker still holds on to the memory that it blocked for those containers and this means downstream processes fail due to lack of RAM.

To counter this, I have powershell scripts to start docker desktop and to kill docker desktop.

All of this is a horrid experience.

On my Mac, I just use Colima with Portainer and couldn't be happier.

I've explored some options to replace Docker Desktop and it seems Rancher Desktop is a drop-in replacement for Docker Desktop, including the docker remote API.

Is this true? Is Rancher Desktop that good of a drop-in replacement?
Does Rancher Desktop better manage RAM for containers that have been killed off? Or does it do the same thing as Docker Desktop and hold on to the RAM?

Are there other options which I'm not thinking of which might solve my problems? I've seen a few alternatives but haven't tried them yet - moby,
containerd,
podman

I don't actually need the Docker Desktop interface. So pure CLI docker would also just work. How are you all running pure docker on Windows boxes?

you are viewing a single comment's thread
view the rest of the comments

[–] damnthefilibuster@lemmy.world 1 points 2 years ago (3 children)

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?

[–] rikudou@lemmings.world 6 points 2 years ago

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.

[–] theterrasque@infosec.pub 2 points 2 years ago* (last edited 2 years ago)

is it able to take as much resources as it needs from the host? Unrestricted in terms of RAM and CPU?

https://learn.microsoft.com/en-us/windows/wsl/wsl-config#configuration-setting-for-wslconfig

[–] breadsmasher@lemmy.world 1 points 2 years ago (1 children)

made things slow

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

Unrestricted

yes

[–] damnthefilibuster@lemmy.world 1 points 2 years ago

nice! Thanks! :)