[pkg-go] Bug#1024809: podman systemd service running as user deletes socket file on termination

Antoine Musso hashar at free.fr
Tue Dec 6 14:22:51 GMT 2022

Le 27/11/2022 à 20:47, Reinhard Tartler a écrit :
> That's an interesting find. It seems to me that you are trying to use
> podman in a similar way like docker, albeit in rootless. While I'm not
> really sure what's the point in using podman in this way, those systemd
> user unit files are shipped upstream.
> I've just checked that the most recent upstream version does not
> pass --time 0 either: 
> https://github.com/containers/podman/blob/main/contrib/systemd/system/podman.service.in <https://github.com/containers/podman/blob/main/contrib/systemd/system/podman.service.in>
> May I ask you to please open an upstream issue at 
> https://github.com/containers/podman/issues/new 
> <https://github.com/containers/podman/issues/new> and report back with 
> the issue number?

Hello Reinhard,

Filing a report upstream was indeed going to be my next step. I 
eventually switched to target the default podman socket (which runs as 
root) since my use case involves the creation of network and Podman 3.0 
does not support that for rootless container.

I had a few other issues such as:
* the dnsname plugin not being installed at the proper location
* golang-github-containernetworking-plugin-dnsname not being usable 
under Bullseye:
** Does not install dnsmasq-base (#985548, #991525)
** The plugin is at /usr/lib/dnsname which prevent it from being 
discovered by podman (fixed by 985549)

And the last one I found is the API service does not have a build cache 
layer https://github.com/containers/podman/issues/12378 (which got 
backported and released in 3.4.3).

Essentially my advanced use case doesn't work with Podman 3.0.1 but it 
works fine with a lot of other things and the CLI is definitely 
pleasant. So at least thank you for the packaging work!

I will try to backport 4.3.1 from testing to Bullseye.

Meanwhile, you can close this bug and if I encounter the issue again I 
will file it directly to upstream (thank you for the helpful pointers!).

Antoine Musso

More information about the Pkg-go-maintainers mailing list