Why do tools still assume Docker when Podman has extreme compatibility? I just want to run a daemonless container technology
@tristan957 I think it's because Podman is not that popular compared to Docker. Docker was "first" and based on my own observation: Nearly no-one in the Windows world ever heard about Podman (even when they use things like GH-Actions or K8s).
I had no issue yet when setting an alias from docker -> podman but I agree that some tools require a very specific environment
@mbeddedDev Might try checking your distro for a podman-docker package. It helps a lot. Unfortunately tooling at work seems to require the docker engine. It is very frustrating.
@tristan957@fosstodon.org Same reason why people still assume "GitHub" when you talk about git. The average developer unironically doesn't understand there are better tools, they've never been taught about the underlying systems to their tools. They also simply seem to not care, so they never wonder what makes their tools actually work.
There doesn't seem to be an easy fix, so all you can really do is try to use the right words for the actual underlying tools to force inferior developers to think about them, and talk about it more.