Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)
Hi Noah, First of all many thanks for the new images and for the help with this bug report. Regarding removing libnss-resolve, that's good to know. I figured doing bullseye->bookworm was not a good strategy long-term anyways, so I decided to look further for a solution, which I found by removing the resolve entries in /etc/nsswitch.conf. But I'll definitely will try by removing libnss-resolve on next installs. For instance, the other issue I was facing turned out not to be related to s-resolved, but to s-networkd not honoring DHCP search domains (for which I'm currently testing a solution and plan to file a bug reports soon, hopefully with a proposed workaround). Regards, On 2024-04-11 20:33, Noah Meyerhans wrote: On Wed, Apr 03, 2024 at 09:39:40PM -0700, Flavio Veloso Soares wrote: Hi Noah - I guess I'll be doing bullseye->bookworm installs in the meantime, until 12.6 so I can fill bug reports (if any). It should be plenty to start with the bookworm images and simply remove the libnss-resolve package. It's quite a lot simpler. noah -- FVS
Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)
On Wed, Apr 03, 2024 at 09:39:40PM -0700, Flavio Veloso Soares wrote: > Hi Noah - I guess I'll be doing bullseye->bookworm installs in the meantime, > until 12.6 so I can fill bug reports (if any). It should be plenty to start with the bookworm images and simply remove the libnss-resolve package. It's quite a lot simpler. noah
Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)
Hi Noah - I guess I'll be doing bullseye->bookworm installs in the meantime, until 12.6 so I can fill bug reports (if any). Appreciate the reply. Thanks for bringing me awareness of the issue in GH. On 2024-04-03 20:01, Noah Meyerhans wrote: Control: tags -1 + pending On Wed, Apr 03, 2024 at 06:48:56PM -0700, Flavio Veloso Soares wrote: Is this the correct forum to report issues/ask question about the official Debian images on AWS? The BTS isn't really the correct forum to ask questions about any Debian topics, but it is the right place to report issues. Note that the plan, as discussed in team meetings and described at https://lists.debian.org/debian-cloud/2024/03/msg00018.html, is to stop installing libnss-resolve as of the upcoming 12.6 release. That will effectively remove systemd-resolved from the name resolution process, leaving it only to manage /etc/resolv.conf. noah -- FVS
Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)
Control: tags -1 + pending On Wed, Apr 03, 2024 at 06:48:56PM -0700, Flavio Veloso Soares wrote: > Is this the correct forum to report issues/ask question about the official > Debian images on AWS? The BTS isn't really the correct forum to ask questions about any Debian topics, but it is the right place to report issues. Note that the plan, as discussed in team meetings and described at https://lists.debian.org/debian-cloud/2024/03/msg00018.html, is to stop installing libnss-resolve as of the upcoming 12.6 release. That will effectively remove systemd-resolved from the name resolution process, leaving it only to manage /etc/resolv.conf. noah
Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)
Hi, Any update on this? Is this the correct forum to report issues/ask question about the official Debian images on AWS? On 2024-02-18 13:09, Flavio Veloso Soares wrote: > Hello, > > Bookworm's release notes clearly states that "systemd-resolved was > not, and still is not, the default DNS resolver in Debian" > (https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#systemd-resolved) > > However apparently it is the default on the Debian provided AWS AMIs > -- at least that's what I got out-of-box on a few instances I > installed recently from the images in > https://wiki.debian.org/Cloud/AmazonEC2Image/Bookworm for the > us-east-2 and ca-west-1 regions. > > Goals here is not to discuss systemd idiosyncrasies, but I've only got > headaches with systemd-resolved/-networkd to the point it's being > easier to install Bullseye and upgrade (...) -- FVS
Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)
Package: cloud.debian.org Severity: important X-Debbugs-Cc: flavi...@magnux.com Hello, Bookworm's release notes clearly states that "systemd-resolved was not, and still is not, the default DNS resolver in Debian" (https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#systemd-resolved) However apparently it is the default on the Debian provided AWS AMIs -- at least that's what I got out-of-box on a few instances I installed recently from the images in https://wiki.debian.org/Cloud/AmazonEC2Image/Bookworm for the us-east-2 and ca-west-1 regions. Goals here is not to discuss systemd idiosyncrasies, but I've only got headaches with systemd-resolved/-networkd to the point it's being easier to install Bullseye and upgrade (no extra systemd-nonsensed then, everything works). So I just want to clarify what's the current status quo regarding systemd-resolved/-networkd in cloud images so I can file bug reports properly. p.s.: same for polkitd -- not sure if we need a daemon "intended to be used by privileged programs offering service to unprivileged programs often through some form of inter-process communication mechanism" installed NOT TO SAY RUNNING on a purposedly minimal network server that virtually can only be acessed via ssh. I'm happy to file a bug report/wishlist item if necessary. Thank you, FVS
