suggestion: rename podman service to avoid conflict with docker service

[AkihiroSuda]

podman service looks as if it was Podman's implementation of docker service.

I suggest renaming podman service to podman daemon, because it seems actually reimplementation of docker daemon that had existed in Docker 1.10 and prior versions.

[mheon]

We're trying to avoid running this as a daemon (using systemd socket-activation, and having a timeout on the command so it's not always on), so podman daemon is probably a bad idea, but I'm not opposed to renaming to ensure we don't conflict.

[mheon]

If so, we should do this quick, before we cut a 1.8.0 final and formalize the name in an official release

[mheon]

@baude @rhatdan @vrothberg PTAL

[AkihiroSuda]

Or maybe podman system service

[vrothberg]

podman listen?

Thanks for pointing that out, @AkihiroSuda !

[rhatdan]

Why would podman service conflict with docker.service?

[rhatdan]

Podman is not listening by default at docker.sock, If you install podman-docker, it will create a linkfile between /run/docker.sock and /run/podman.sock. But podman-docker conflicts with docker-* packages.

[vrothberg]

There's a docker service command -> https://docs.docker.com/engine/reference/commandline/service/

[rhatdan]

So this is their replacement for dockerd? If it is, then podman service makes sense. Except for not listening on docker.sock?

[mheon]

No, it's a swarm command, AFAIK - it launches a service via swarm

[rhatdan]

Well we have said we will not support Docker swarm, does it matter we have the same name?

[mheon]

Potential confusion? I'd prefer not to knowingly conflict with Docker commands if we can afford not to

[rhatdan]

Fine, except that if we come up with a strange name for this service.
podman restapi
podman server

[mheon]

podman server sounds good to me

[mheon]

podman system service also works for me

[rhatdan]

Yes I like keeping it under system.