---
title: "containers/podman-compose: a script to run docker-compose.yml ..."
description: "!https://github.com/containers/podman-compose"
date: 2025-01-09
published: true
tags:
  - thought
template: link
---


<div class="embed-card embed-card-external">
  <a href="https://github.com/containers/podman-compose" class="embed-card-link" target="_blank" rel="noopener noreferrer">
    <div class="embed-card-image">
      <img src="https://opengraph.githubassets.com/ebdb092e0ed5b3667a0135f9df761a5a359883e7d284e5e04ed6feb2c974cb6f/containers/podman-compose" alt="GitHub - containers/podman-compose: a script to run docker-compose.yml using podman — a script to run docker-compose.yml using podman. Contribute to containers/podman-compose development by creating an account on GitHub." loading="lazy">
    </div>
    <div class="embed-card-content">
      <div class="embed-card-title">GitHub - containers/podman-compose: a script to run docker-compose.yml using podman</div>
      <div class="embed-card-description">a script to run docker-compose.yml using podman. Contribute to containers/podman-compose development by creating an account on GitHub.</div>
      <div class="embed-card-meta">GitHub &middot; github.com</div>
    </div>
  </a>
</div>


Wild that the podman-compose github readme calls out k3s as an alternative.

![image](https://dropper.waylonwalker.com/api/file/9326cd6f-3f27-4703-85fd-a3b16f7bdc92.webp)

compose definitely has its place, especially for local development on a developers machine, its so much easier to stand up and get things like hot reload up and running smooth.