this post was submitted on 27 Aug 2023
46 points (94.2% liked)

Selfhosted

60451 readers
991 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

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

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

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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.

  1. Is this true? Is Rancher Desktop that good of a drop-in replacement?
  2. 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
[–] nickwitha_k@lemmy.sdf.org 7 points 2 years ago (3 children)

If you don't need UI, I prefer Podman. Rancher Desktop is good though.

[–] loren@programming.dev 6 points 2 years ago

Podman Desktop is also a thing

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

thanks! So podman supports the docker API completely?

[–] frankivo@feddit.nl 4 points 2 years ago (2 children)

Drop-in replacement as far as I can tell after using it for some time

[–] TrustingZebra@lemmy.one 6 points 2 years ago (1 children)

This is a common misconception. Podman has similar commands to Docker CLI but it's not a "drop-in replacement". Depending on your usage, you might run into things that don't work the same.

[–] frankivo@feddit.nl 1 points 2 years ago

Interesting, thanks!

[–] russjr08@outpost.zeuslink.net 3 points 2 years ago

Yep! You can even just alias the docker command to podman, and most things will work just fine. Podman can also expose a socket that is compatible with the Docker API for anything that requires it too.

[–] marty@discuss.tchncs.de 1 points 2 years ago

Yes, rancher desktop works perfectly 👍🏻