Most active commenters

    ←back to thread

    221 points finnlab | 11 comments | | HN request time: 0.523s | source | bottom
    1. raphinou ◴[] No.43545661[source]
    Exactly, my first reaction was "I should write a blog post about why I still use Docker Swarm". I deploy to single node swarms, and it's a zero boiler plate solution. I had to migrate services to another server recently, and it was really painless. Why oh why doesn't Docker Swarm get more love (from its owners/maintainers and users)?....

    Edit: anyone actually interested in such a post?

    replies(9): >>43545769 #>>43545842 #>>43546429 #>>43546455 #>>43546541 #>>43547576 #>>43549257 #>>43549367 #>>43549757 #
    2. mfashby ◴[] No.43545769[source]
    I moved us off docker swarm to GKE some years back. The multi node swarm was quite unstable, and none of the big cloud providers offered managed swarm in the same way they offer managed k8s.

    It's a shame I agree because it was nicely integrated with dockers own tooling. Plus I wouldn't have had to learn about k8s :)

    3. galbar ◴[] No.43545842[source]
    I just want to add that I also have a Docker Swarm running, with four small nodes for my personal stuff plus a couple of friends' companies.

    No issues whatsoever and it is so easy to manage. It just works!

    4. gmm1990 ◴[] No.43546429[source]
    I'd be interested. Might be a strange question but I'll throw it out there, I seem to have a hard time finding a good way to define my self hosted infrastructure nodes and which containers can run on them, have you run into/have a solution for this? Like I want my database to run on my two beefier machines but some of the other services could run on the mini pcs.
    replies(1): >>43547536 #
    5. resiros ◴[] No.43546455[source]
    yes, please.
    6. quectophoton ◴[] No.43546541[source]
    > I deploy to single node swarms, and it's a zero boiler plate solution.

    Yup, it's basically like a "Docker Compose Manager" that lets you group containers more easily, since the manifest file format is basically Docker Compose's with just 1-2 tiny differences.

    If there's one thing I would like Docker Swarm to have, is to not have to worry about which node creates a volume, I just want the service to always be deployed with the same volume without having to think about it.

    That's the one weakness I see for multi-node stacks, the thing that prevents it from being "Docker Compose but distributed". So that's probably the point where I'd recommend maybe taking a look at Kubernetes.

    7. raphinou ◴[] No.43547536[source]
    I am running one-node swarms, so everything I deploy is running on the same node. But from my understanding you can apply labels to the nodes, and limit the placement of containers. See here for an example (I am not affiliated to this site): https://www.sweharris.org/post/2017-07-30-docker-placement/
    8. StrLght ◴[] No.43547576[source]
    I am very interested. I tried to migrate to Swarm, got annoyed at incompatibility with tons of small Docker Compose things, and decided against that. I'd love to read about your setup.
    9. opsdisk ◴[] No.43549257[source]
    Would love a blog post on how you're using Docker Swarm.
    10. kiney ◴[] No.43549367[source]
    bugs in it's infancy is what killed swarm for users.
    11. ndsipa_pomu ◴[] No.43549757[source]
    Yep. I run a small swarm at work and have a 5-node RPi-4 swarm at home. Interested in why you'd run a single-node swarm instead of stand-alone docker.