<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on Dayio.dev</title><link>https://dayio.dev/tags/docker/</link><description>Recent content in Docker on Dayio.dev</description><generator>Hugo</generator><language>en-us</language><copyright>© Dayio</copyright><lastBuildDate>Tue, 17 Feb 2026 22:49:15 +0200</lastBuildDate><atom:link href="https://dayio.dev/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Docker Swarm is still My Go-To in 2026</title><link>https://dayio.dev/posts/why-docker-swarm-is-still-my-go-to-in-2026/</link><pubDate>Tue, 17 Feb 2026 22:49:15 +0200</pubDate><guid>https://dayio.dev/posts/why-docker-swarm-is-still-my-go-to-in-2026/</guid><description>&lt;p&gt;I still remember the early days of containerization. Back then, I deployed a DC/OS cluster for production apps with Marathon, all running on top of Mesos. Kubernetes already existed, but it was incredibly complex for my needs and too hard to set up.&lt;/p&gt;
&lt;p&gt;I followed the trends and the evolution of K8s for a long time. I wrote manifests for all my apps, set up CD pipelines with ArgoCD and FluxCD (why not both ?), and tested managed K8s with autoscaling. But something just felt off. I’m a &amp;ldquo;simple&amp;rdquo; backend engineer who does a lot of sysadmin and DevOps work, and Kubernetes simply felt like overkill.&lt;/p&gt;</description></item></channel></rss>