Comment by nwienert

Comment by nwienert 21 hours ago

10 replies

View on Hacker News

First - I really want something like this to exists and be great, so best of luck. As of today I'd consider this or Dokploy (Docker Swarm is underrated).

Small feedback - your "Why you should NOT use Canine" section actually is a net-negative for me. I actually was thinking it was cool that it may actually list downsides, but then you did a sarcastic thing that was annoying. I think you should just be frank - you'll have to purchase and manage servers, you'll be on the hook if they go down and have to get them back up, this is an early product made by one person, etc.

dgellow 6 hours ago

What’s the state of docker swarm? I stopped following years ago when it felt the software has been abandoned by the docker team

Reply View 5 replies
  • vbezhenar 6 hours ago

    It is supported by docker and not abandoned. I just checked latest docker engine release notes and there are multiple fixes and enhancements. Certainly not as popular, compared to Kubernetes, but it is there.

    Reply View 4 replies
    • horsawlarway 3 hours ago

      Eh, it's not quite that simple.

      What the person above you is thinking of is almost certainly "swarm classic" which is actually dead (see: https://github.com/docker-archive/classicswarm)

      Docker does support a different "Swarm mode" style deployment configuration, which is functionally https://github.com/moby/swarmkit, and really feels much more like Kubernetes to me than the original docker swarm.

      I'm... honestly not sure why you'd pick it as a solution over all the k8s tooling they've been doing instead. It feels like the same level of complexity and then only benefit is that it's easier to configure than bare metal k8s, but things like k3s and microk8s tackle that same space.

      If anyone is really using the swarm mode for a production service, I'd love to hear different opinions, though!

      Reply View 3 replies
      • 0xbadcafebee 2 hours ago

        If I were going to build out bare-metal k8s, I would first try Swarm instead. I would not use k3s or an alternative. The biggest problem with k8s (any version of it) is its overall cost in expertise and maintenance is incredibly high (if you're doing it right; many people are completely ignorant to how terribly they're maintaining it and assume their cost is low). Swarm's cost is going to be significantly smaller, both in the short and long term.

        Reply View 1 reply
        • horsawlarway 21 minutes ago

          Can you speak more precisely about what costs you think something like k3s imposes that are solved by swarm?

          Right now this comment has the same kind of FUD that I see in the swarm docs (there is no "why" to swarm in the docker published docs that feels particularly compelling, especially given the amount of time and energy docker seems to be putting into their k8s tooling instead).

          I'm willing to bite - but I run a baremetal cluster on k3s, and it's very simple to keep up to date.

          Reply View 0 replies
      • [removed] 2 hours ago
        [deleted]
        Reply View 0 replies
czhu12 19 hours ago

Haha, well there goes my attempt to be different from the other landing pages out there. I'll take another stab, but appreciate the feedback!

Reply View 2 replies