In my experience podman compose is not a sufficient replacement.
Docker compose can be used with podman via the podman socket daemon. It’s very easy to get working. Give it a try.
In my experience podman compose is not a sufficient replacement.
Docker compose can be used with podman via the podman socket daemon. It’s very easy to get working. Give it a try.
Oops. Thanks for the correction.
I hadn’t heard of quadlets. I’ll have to give them a look.
We’ve completely transitioned from docker to podman where I work. The only pain point was podman compose being immature compared to docker compose, but turns out you can run docker compose with podman using the podman socket easily.
Some of the “misleading” statements were Harris neglecting to enumerate the reasons why a stated policy goal might not succeed, which would be incredibly unusual to include in a speech of this nature.
I guess the point the author was trying to make was that saying you “will” do something in office is a promise, and if you don’t have the ability to guarantee that promise can be kept you shouldn’t say that thing at all? I love me some NPR but they’re really bending over backwards with some of these…
Agree. I may be misunderstanding something here, but to view votes one would have to spin up their own instance. This would prevent your average abusive moron from harassing users who down voted their post/comment.
I’ll have to give it another try.
I should clarify that the issues I had were podman compose being able to run unaltered compose files that worked with docker compose, many of which were fairly complicated. It may have been adequate for simpler use cases back when I tried it.