Your message dated Sun, 17 Dec 2017 23:07:15 +0000 with message-id <e1eqi1b-0003zg...@fasolo.debian.org> and subject line Bug#881310: fixed in systemd 236-1 has caused the Debian Bug report #881310, regarding systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf 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.) -- 881310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: systemd-container Version: 232-25+deb9u1 Severity: normal Tags: upstream Dear Maintainer, After installing the package to get systemd-nspawnd, I created an etch image with: # cd /var/lib/machines # debootstrap --variant=minbase --no-check-gpg --arch=i386 etch etchruby \ http://archive.debian.org/debian/ This system can't resolve DNS names: # systemd-nspawn --directory etchruby/ Spawning container etchruby on /var/lib/machines/etchruby. Press ^] three times within 1s to kill container. etchruby:~# apt-get update Err http://archive.debian.org etch Release.gpg Temporary failure resolving 'archive.debian.org' Failed to fetch http://archive.debian.org/debian/dists/etch/Release.gpg Temporary failure resolving 'archive.debian.org' Reading package lists... Done E: Some index files failed to download, they have been ignored, or old ones used instead. /etc/resolv.conf inside the container is apparently bind-mounted from the host's /lib/systemd/resolv.conf, and cannot be modified inside the container. This is probably only a problem for non-systemd containers, as systemd presumably has some workaround. It also presumably is only a problem if systemd-resolved is not used (as is standard in Debian.) This appears to be identified at https://github.com/systemd/systemd/issues/4649 and closed in https://github.com/systemd/systemd/pull/5369, not sure if that's made it in to a release yet. Would be nice to have a fix for this in Debian. -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.4.96-rh115-20171102201402.xenU.x86_64 (SMP w/1 CPU core) Locale: LANG=en_NZ.utf8, LC_CTYPE=en_NZ.utf8 (charmap=UTF-8), LANGUAGE=en_NZ.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-container depends on: ii dbus 1.10.22-0+deb9u1 ii libacl1 2.2.52-3+b1 ii libblkid1 2.29.2-1 ii libbz2-1.0 1.0.6-8.1 ii libc6 2.24-11+deb9u1 ii libcurl3-gnutls 7.52.1-5+deb9u2 ii libgcrypt20 1.7.6-2+deb9u2 ii libip4tc0 1.6.0+snapshot20161117-6 ii liblzma5 5.2.2-1.2+b1 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3+b3 ii systemd 232-25+deb9u1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages systemd-container recommends: ii btrfs-progs 4.7.3-1 ii libnss-mymachines 232-25+deb9u1 systemd-container suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: systemd Source-Version: 236-1 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <bi...@debian.org> (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 17 Dec 2017 21:45:51 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 236-1 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org> Description: libnss-myhostname - nss module providing fallback resolution for the current hostname libnss-mymachines - nss module to resolve hostnames for local container instances libnss-resolve - nss module to resolve names via systemd-resolved libnss-systemd - nss module providing dynamic user and group name resolution libpam-systemd - system and service manager - PAM module libsystemd-dev - systemd utility library - development files libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) systemd - system and service manager systemd-container - systemd container/nspawn tools systemd-coredump - tools for storing and retrieving coredumps systemd-journal-remote - tools for sending and receiving remote journal logs systemd-sysv - system and service manager - SysV links systemd-tests - tests for systemd udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 878965 879603 881310 881823 882245 882270 883380 883407 883605 Changes: systemd (236-1) unstable; urgency=medium . [ Martin Pitt ] * debian/tests/upstream: Only show ≥ warning in journal dumps. Showing the entire debug log is too hard to scan visually, and most of the time the warnings and errors are sufficient to explain a failure. Put the journal files into the artifacts though, in case the debug information is necessary. . [ Michael Biebl ] * New upstream version 236 - nspawn: Adjust path to static resolv.conf to support split usr. (Closes: #881310) - networkd: Don't stop networkd if CONFIG_FIB_RULES=n in kernel. (Closes: #881823) - core: Fix segfault in compile_bind_mounts() when BindPaths= or BindReadOnlyPaths= is set. (Closes: #883380) - meson: Link NSS modules with -z nodelete to fix memory leak in nss-systemd. (Closes: #883407) - logind: Make sure we don't acces m->action_what if it's not initialized. (Closes: #882270) - systemctl: Ignore shutdown's "-t" argument. (Closes: #882245) - core: Be more defensive if we can't determine per-connection socket peer. (Closes: #879603) - bpf-firewall: Actually invoke BPF_PROG_ATTACH to check whether cgroup/bpf is available. (Closes: #878965) * Rebase patches * Update symbols file for libsystemd0 * Bump Standards-Version to 4.1.2 * Clean up old /var/lib/systemd/clock on upgrade. The clock file used by systemd-timesyncd is now stored in StateDirectory=systemd/timesync. (Closes: #883605) * Stop creating systemd-timesync system user. DynamicUser=yes has been enabled for systemd-timesyncd.service so allocating a system user statically is no longer necessary. * Document removal of systemd-{timesync,journal-gateway,journal-upload} user. We no longer create those system users as the corresponding services now use DynamicUser=yes. Removing those system users automatically is tricky, as the relevant services might be running during upgrade. Add a NEWS entry instead which documents this change. * Revert "udev-rules: Permission changes for /dev/dri/renderD*" This would introduce a new system group "render". As the name is rather generic, this needs further discussion first, so revert this change for now. Checksums-Sha1: 70c608138be09f2ba887024672cbb83491d9e2be 4836 systemd_236-1.dsc eab372a3441997dfba1dfa41183918764c31a7df 6759035 systemd_236.orig.tar.gz 2907f79997ed5b4e1bf666f895ce660c8e81e032 133060 systemd_236-1.debian.tar.xz ce3d4e6793bce488e1bf6c0066d2bebc0484ca45 9879 systemd_236-1_source.buildinfo Checksums-Sha256: d44f58c1c62861bcf727c45657c15cc523d3536aa211e020adbc6010337c1554 4836 systemd_236-1.dsc 0cadccfa7109232ec2a469d41ca595d5595b83b648b534ea669c15dbca904c43 6759035 systemd_236.orig.tar.gz ed649a65b8adc730d9261d572b8214ea487c8a2c5afda0c448df43d16c5adf65 133060 systemd_236-1.debian.tar.xz b57fdc331ac965882e03a74c7cd306d9824dae97f4023e9ecfc58b01a7008682 9879 systemd_236-1_source.buildinfo Files: 5383372632b2425bfe17fb93239f7cd3 4836 admin optional systemd_236-1.dsc 8609cb9043ac8f374371cbac5546acf4 6759035 admin optional systemd_236.orig.tar.gz e92885c9e76cf0a8c852b8e16d2bc37e 133060 admin optional systemd_236-1.debian.tar.xz 52ff8043aebbc02ce9dc20f575982e55 9879 admin optional systemd_236-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlo28soACgkQauHfDWCP ItyFkQ/7B2ijLMVUAsiytDaZA+L5weyPsQ/hPruYaXXxCjDdNqQhIztUVkHgGuFr XI/uhNUcinq76tlK+h6Q8vFleiE+NMueVSymXSogwSzTFGi45en/gxf55wdBnaHF dKRgzkGGIshRJcQ+b9t8kEbxK0tBTTRu0Q1V4i0w061w5e0OJDoL7BaLIktPcpq7 G5+o2G1ixA9VMq7FGjTyR8UBMrCVA0g2Nx7UsSDSzPlKKL6krSi2zg6u7Aro8ZRm ir5zqFmVio34E9GjuDyAItFbGgdOa44uGFpcOMGirTe87GH/V8EOfZrU9kLaGufm 9hz4I6YlC60+x3+dGP1xsv+hCA3ebZ4624INRyzfYqzxhcaGrerg4OZKNxTHxDBj 8gubt/miJh1OSqvtYjpTH4dYbW5uIj1q2p75zx6UuItRvuInY3+Ee6Nzzo6gLGqE OfKsQtmppU7CWvou3l/M39dcGpb+OsVpMljHvodEsLSaiXDdIl4BCmu31J6Uj6EW VMXhttDslXkM/N1xt3HxbsKfcqm9Bx9iSPYJ1xz35WiS9YWp57qlxCTYlIjm+swH +qTAFmU01CWNvFvM36BMKebFKOjDjnw0YxpIWfNqRBwMYLxL3bl/9WFnwOUiUUqr lBZSVKT8u8yU2XizseJX2BXNXZ1bNUctc69Y3HjLIMb1boiqM6k= =DC/B -----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
