Skip to content

Why Docker Swarm?

Pop quiz, hotshot.. There's a server with containers on it. Once you run enough containers, you start to loose track of compose files / data. If the host fails, all your services are unavailable. What do you do? WHAT DO YOU DO?1

You too, action-geek, can save the day, by...

  1. Enable Docker Swarm mode (even just on one node)2
  2. Store your swarm configuration and application data in an orderly and consistent structure

  3. Expose all your services consistently using Traefik with optional additional per-service authentication

    Then you can really level-up your geek-fu, by:

  4. Making your Docker Swarm highly with keepalived

  5. Setup shared storage to eliminate SPOFs
  6. Backup your stuff automatically

Ready to enter the matrix? Jump in on one of the links above, or start reading the design

Chef's notes 📓

  1. This was an iconic movie. It even won 2 Oscars! (but not for the acting) ↩

  2. There are significant advantages to using Docker Swarm, even on just a single node. ↩

Tip your waiter (sponsor) 👏

Did you receive excellent service? Want to compliment the chef? (..and support development of current and future recipes!) Sponsor me on Github / Ko-Fi / Patreon, or see the contribute page for more (free or paid) ways to say thank you! 👏

Employ your chef (engage) 🤝

Is this too much of a geeky PITA? Do you just want results, stat? I do this for a living - I'm a full-time Kubernetes contractor, providing consulting and engineering expertise to businesses needing short-term, short-notice support in the cloud-native space, including AWS/Azure/GKE, Kubernetes, CI/CD and automation.

Learn more about working with me here.

Flirt with waiter (subscribe) 💌

Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated.

Your comments? 💬