<story><title>Podman Desktop 1.2 Released: Compose and Kubernetes Support</title><url>https://podman-desktop.io/blog/podman-desktop-release-1.2</url></story><parent_chain><item><author>flatline</author><text>Docker swarm is supposed to be the migration target for these cases, but I’ve never actually used it.</text></item><item><author>brazzledazzle</author><text>Docker compose falls apart when you need something clustered across nodes or any other multi-host deployment. Once you have to rip it apart it becomes way less appealing. Though I haven&amp;#x27;t tried it in a while and perhaps the ergonomics have changed.</text></item><item><author>jadbox</author><text>I&amp;#x27;m very happy to see you better support for docker compose. I think about 50% of the time I find Kubernetes used in production&amp;#x2F;development when it could have just used Compose along with a simple Terraform or Pulumi deploy script.</text></item></parent_chain><comment><author>belthesar</author><text>I&amp;#x27;ve done some labbing with Swarm. Swarm is _just different enough_ to be a pain, but just similar enough to fool you into thinking you know what you&amp;#x27;re doing. Because swarm was also confused terminology (at one point there were two things with the name swarm that did things differently) the tech definitely got a bad rap for a while, but it also stagnated supporting tooling. You can use things like Portainer and Swarmpit to get some visibility into your swarm cluster members, deploy workloads, etc, but it definitely feels like a second class citizen.&lt;p&gt;Ultimately, I would love for something to exist out there that had the opinions and scope of deployment like Swarm in terms of simplicity, but didn&amp;#x27;t conflate other tools out there so that ergonomics and documentation were better and less confusing. Kubernetes gives you so much, but I do feel like it&amp;#x27;s a misstep that the only reasonable way we&amp;#x27;ve simplified Kubernetes for production workflows is to pay a large PaaS to manage it for us.</text></comment>
<story><title>Podman Desktop 1.2 Released: Compose and Kubernetes Support</title><url>https://podman-desktop.io/blog/podman-desktop-release-1.2</url></story><parent_chain><item><author>flatline</author><text>Docker swarm is supposed to be the migration target for these cases, but I’ve never actually used it.</text></item><item><author>brazzledazzle</author><text>Docker compose falls apart when you need something clustered across nodes or any other multi-host deployment. Once you have to rip it apart it becomes way less appealing. Though I haven&amp;#x27;t tried it in a while and perhaps the ergonomics have changed.</text></item><item><author>jadbox</author><text>I&amp;#x27;m very happy to see you better support for docker compose. I think about 50% of the time I find Kubernetes used in production&amp;#x2F;development when it could have just used Compose along with a simple Terraform or Pulumi deploy script.</text></item></parent_chain><comment><author>e12e</author><text>Swarm works, but has poor support for volumes - which means it&amp;#x27;s tricky to run legacy applications on swarm (which eg uploads files to local disk, not s3 - or keeps state&amp;#x2F;cache on disk, not a database).&lt;p&gt;Ingress is also more complicated&amp;#x2F;bespoke - the best I&amp;#x27;ve found is traefik with labels for routing&amp;#x2F;config.&lt;p&gt;My advice today would be to scale Docker compose vertically (eg: on a dedicated server) - then move to Kubernetes.&lt;p&gt;The swarm middle ground isn&amp;#x27;t really worth it IMNHO.</text></comment>