Your message dated Mon, 10 Apr 2023 17:45:13 -0400
with message-id
<CAJ0cceY04D3Hkfvbsb6k0d+6Km=qVpOWvcPcMTCSEubn==y...@mail.gmail.com>
and subject line Re: Bug#1017766: podman: Failed to activate DNS. Missing
dependency on golang-github-containernetworking-plugin-dnsname
has caused the Debian Bug report #1017766,
regarding podman: Failed to activate DNS. Missing dependency on
golang-github-containernetworking-plugin-dnsname
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1017766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 4.2.0+ds1-3
Severity: important
Hi,
thanks for bringing up-to-date podman packages to Debian. This is really nice
to have those current version available.
With the latest version of the podman packages (4.2.0+ds1-3) dns resolution
fails for podman networks.
This could simply be resolved by installing
'golang-github-containernetworking-plugin-dnsname'. I think this should be
installed automatically via dependencies.
hth, keep up the nice work
regards Michael
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (504, 'unstable'), (503, 'testing'), (502, 'experimental'), (1,
'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages podman depends on:
ii conmon 2.1.3+ds1-1
ii crun 1.5+dfsg-1+b1
ii golang-github-containers-common 0.49.1+ds1-1
ii libc6 2.34-4
ii libdevmapper1.02.1 2:1.02.185-1
ii libgpgme11 1.17.1-4
ii libseccomp2 2.5.4-1+b1
ii runc 1.1.3+ds1-7
ii systemd [systemd-tmpfiles] 251.4-1
Versions of packages podman recommends:
ii buildah 1.27.0+ds1-5
ii catatonit 0.1.7-1
ii dbus-user-session 1.14.0-2
ii fuse-overlayfs 1.9-1
ii slirp4netns 1.2.0-1
ii tini 0.19.0-1
ii uidmap 1:4.11.1+dfsg1-2
Versions of packages podman suggests:
ii containers-storage 1.42.0+ds1-1
ii docker-compose 1.29.2-1
ii iptables 1.8.8-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Michael,
On Sat, Sep 10, 2022 at 1:47 PM Reinhard Tartler <siret...@gmail.com> wrote:
> On Sat, Aug 20, 2022 at 5:47 PM Michael Musenbrock <
> michael.musenbr...@gmx.at> wrote:
>
>>
>>
>> Now a dns-server is active in the network, but the other pods attached to
>> the network
>> still can't be resolved. But this may be just some config issue. I will
>> check.
>>
>>
> just checking in, did you had a chance to check whether this is a config
> issue?
>
> In any case, any chance you could describe your test setup? I'm still
> looking
> for a minimal test case that would be able to demonstrate the issue, and
> thought
> you might be able to help?
>
>
Unfortunately, I haven't heard back from you in many months. I'm therefore
going to close
this bug report for now. If you have any additional information or
suggestions how
I could reproduce this issue, please don't hesitate to respond to this
email and make
sure to copy 1017...@bugs.debian.org in your response.
Thanks!
--
regards,
Reinhard
--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
