News for hackers. Stuff that matters.

A comment on Rancher Desktop, a Docker Desktop Replacement. Parent comment

Re:Rancher Desktop, a Docker Desktop Replacement by GordonS on Tuesday October 12, 2021 @04:53AM (#28837540)
Ach, the title seems to be mis-selling it.

Docker Desktop is all about Docker, Compose and Swarm, and has Kubernetes functionality built on top as an extra. Rancher Desktop seems to be all about Kubernetes - can it even run standalone Docker containers, or Compose/Swarm services?

EDIT: answering my own question - I checked the nerdctl GitHub page, and it states that not only is Swarm not supported, but it will not be. So Rancher Desktop is unfortunately not a drop-in Docker Desktop replacement for everyone :(

[ Parent | on HN ]
Re:Rancher Desktop, a Docker Desktop Replacement by chupasaurus on Tuesday October 12, 2021 @08:32AM (#28838877)
Swarm is a cluster solution made on top of Compose so it isn't useful on a local machine.
[ Parent | on HN ]
Re:Rancher Desktop, a Docker Desktop Replacement by GordonS on Tuesday October 12, 2021 @10:32AM (#28840169)
It's very useful on a local machine if you're using Swarm in production, as Swarm supports some additional things that Compose doesn't.
[ Parent | on HN ]
Re:Rancher Desktop, a Docker Desktop Replacement by chupasaurus on Tuesday October 12, 2021 @02:37PM (#28843365)
The differences are:

- Replicas: could be made with YAML templating

- Update/rollback policies other than stop-first, very useful on a local machine?

- Resource limits: stayed in v2 to sell Swarm, although there's cgroup_parent which has to be created manually

[ Parent | on HN ]
Re:Rancher Desktop, a Docker Desktop Replacement by GordonS on Tuesday October 12, 2021 @03:09PM (#28843790)
There are yet more differences.

For example, Swarm supports `configs`, while Compose does not - and I use `configs`, and would much rather not have to have separate service definitions for dev and prod to work around such insufficiencies.

[ Parent | on HN ]