[pkg-go] Bug#1107134: podman: DNS resolution fails during startup

[Reinhard Tartler]

Control: tag -1 upstream moreinfo

Hi Jan, thanks for reaching out.


Jan-Nick Kemming <contact at jkemming.com> writes:

>
> I'm trying out Podman Quadlets on trixie and ran into an issue. I've
> reproduced a minimal setup using a clean install inside a VM:
>
> * Installed Debian trixie without a Desktop environment
> * Installed Podman
> * Switched to root and created two files (see content below):
>   * `/etc/containers/systemd/nginx.container`
>   * `/etc/containers/systemd/nginx.image`
> * Rebooted
> * Problem: The generated `nginx-image` service fails to start,
> apparently because the DNS server refused connection (see error
> message below)
>
> Some notable observations:
>
> * The same thing happens every time the machine boots.
> * I couldn't reproduce the problem when I installed the Gnome desktop environment
> * If I manually start the service after booting, it works.
> * Adding a slight delay via `ExecStartPre=/bin/sleep 3` fixes the problem as well.
> * The same thing happens for `.build` Quadlets.
>
> While the sleep fix works fine for the moment, it'd be very nice to
> have a proper fix for this. Please let me know if I can assist
> further, I'd be glad to debug some more if that helps.

First, please upgrade to podman 5.6, which is current about to migrate
from unstable to testing. If the issue still persists, then this is
either a bug in the upstream code or an integration issue into the
distribution, both of which require further investigation.

I need you to work with upstream on resolving this. For doing so, please
go to https://github.com/containers/podman/discussions and start a new
thread. From there, community members and/or upstream developers can
direct you on the best next steps.

Best of luck,
-rt