<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>windexh8er</author><text>I could very well be wrong but Podman seems to have missed the time-frame of opportunity.  It was always a knife fight between Red Hat and Docker with regard to tooling.  Red Hat wanting to own the toolchain for containers so they didn&amp;#x27;t have to deal with, and so they could box out, competitors like (now basically defunct) Docker Enterprise.&lt;p&gt;I&amp;#x27;ve taken a look at podman from time to time over the years but it seems like it&amp;#x27;s just never formalized, never been polished and almost always has been sub-par in execution.  On this list the builds and container control are things that I&amp;#x27;ve run across.  I guess - what&amp;#x27;s the point?  The rootless argument leaned on so heavily is pretty much gone, the quality of Podman hasn&amp;#x27;t (seemingly) improved and now IBM owns Red Hat (subjective, but a viable concern&amp;#x2F;consideration given what&amp;#x27;s recently happened with CentOS).&lt;p&gt;You&amp;#x27;re more than safe leveraging Docker and buildkit (when and where needed).  Quite honestly, given the relatively poor execution of Red Hat with these tools over the years, I don&amp;#x27;t see the point.  I&amp;#x27;m sure there are some niche use cases for Podman&amp;#x2F;Buildah, but overall it just seems to come up as an agenda more than an exponentially better product at this point.  Red Hat could have made things better, instead they just created a distraction and worked against the broader effort in the container ecosystem.</text><parent_chain><item><author>yobert</author><text>I&amp;#x27;ve been trying to use podman in production and it is not working very well. I&amp;#x27;m excited for this technology but it is not ready.&lt;p&gt;- podman layer caching during builds do not work. When we switched back to docker-ce, builds went from 45 minutes to 3 minutes with no changes to our Dockerfile&lt;p&gt;- fuse-overlayfs sits at 100% CPU all day, every day on our production servers&lt;p&gt;- podman loses track of containers. Sometimes they are running but don&amp;#x27;t show in podman ps&lt;p&gt;- sometimes podman just gets stuck and can&amp;#x27;t prune or stop a container&lt;p&gt;(edit: formatting)</text></item></parent_chain></comment><story><title>Podman: A Daemonless Container Engine</title><url>https://podman.io/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dastx</author><text>I&amp;#x27;ve been running multiple services through podman on a pi without any issues. Certainly not the same as production though.&lt;p&gt;Layer caching seems to work for me. Note that rootless stores images (and everything else), in different place from rootfull. It may be that you&amp;#x27;re caching the wrong directory.</text><parent_chain><item><author>yobert</author><text>I&amp;#x27;ve been trying to use podman in production and it is not working very well. I&amp;#x27;m excited for this technology but it is not ready.&lt;p&gt;- podman layer caching during builds do not work. When we switched back to docker-ce, builds went from 45 minutes to 3 minutes with no changes to our Dockerfile&lt;p&gt;- fuse-overlayfs sits at 100% CPU all day, every day on our production servers&lt;p&gt;- podman loses track of containers. Sometimes they are running but don&amp;#x27;t show in podman ps&lt;p&gt;- sometimes podman just gets stuck and can&amp;#x27;t prune or stop a container&lt;p&gt;(edit: formatting)</text></item></parent_chain></comment><story><title>Podman: A Daemonless Container Engine</title><url>https://podman.io/</url></story>