Closed flouthoc closed 3 months ago
@rgrandl @mwhittaker PTAL
This is interesting. Podman provides a similar CLI to docker, so supporting Podman seems pretty straightforward.
Do you know if Podman is widely popular, and what tools people generally use to build and push images? I am worried that once we have a knob for the build tool, people might ask to support many different tools, and they might have completely different CLIs from Docker.
@rgrandl Podman is very popular and it has lot perks as compared to docker. I don't think it is fair to call one better over another. But there are places were podman is better suited than docker. Consider lightweight CI/CD environments where running a daemon is hard and it is undesirable to configure a daemon only for builds
I think in such places podman is much better and by default it offers rootless
users to build container images with ease. ( cc @rhatdan please feel free to correct me if i missed anything here )
I am worried that once we have a knob for the build tool, people might ask to support many different tools, and they might have completely different CLIs from Docker.
That is a fair concern, Two popular tools which I know are podman
and docker
and I think if service-weaver sticks to the point that it has no problem in supporting tools which are docker compatible then there should be no issue, right ? And in documentation this can be written that service-weaver supports docker and will accept PR where build tool is compatible with docker CLI
?
Personally I am using service-weaver with podman
and with this PR i was able to use it without any issues. Since podman is one-to-one compatible with docker I don't think that there is going to be any maintenance overhead in future as well.
Thanks this makes sense to me.
Serviceweaver as of now supports
docker
as the defaultbuild
andpush
tool following PR adds support forpodman
sincepodman
's CLI is directly compatible withdocker
and supports bothrootless
androotful
for build and push.