This bug was fixed in the package docker.io - 20.10.7-0ubuntu3
---
docker.io (20.10.7-0ubuntu3) impish; urgency=medium
* d/t/docker-in-lxd:
Perform a full upgrade and restart of the container before attempting
to install docker.io. (LP: #1942276)
-- Sergio Durigan Junior
This bug was fixed in the package glibc - 2.34-0ubuntu2
---
glibc (2.34-0ubuntu2) impish; urgency=medium
* d/patches/ubuntu/Fix-close_range-closefrom-tests.patch: Patch from
upstream to fix test failures in autopkgtest environment (which has a
pair of fds open that the test
I've uploaded a glibc fix now and it appears to fix the bug so I'll go
ahead and remove the block-proposed tag.
** Changed in: glibc (Ubuntu)
Status: Confirmed => Fix Committed
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942276
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: docker.io (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942276
Title:
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942276
Title:
glibc 2.34 upgrade will break some essential services
To manage notifications about this bug go to:
OK, with thanks to Julian and Dimitri, I think this patch
https://paste.ubuntu.com/p/Bf9tDggMvv/ to glibc will avoid the issue and
avoid the worst part of the referenced debian bug (the kernel panic). It
means another glibc upload though :(
--
You received this bug notification because you are a
Oh right! Yes that explains everything. I filed an upstream bug
https://sourceware.org/bugzilla/show_bug.cgi?id=28300 although I'm not
really sure what I expect them to do about it. The obvious thing to do
would be to reexec systemd on upgrade but as
https://sourceware.org/pipermail/libc-alpha/2021-June/127273.html
stuff from nss_files was moved into glibc proper.
for libnss-db, we addressed this by no longer explicitly linking against
-lnss_files.
LP: #1939918
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Wait a minute...
root@upgrade-testing:~# readelf --wide -s /usr/lib/x86_64-linux-
gnu/libnss_files.so.2
Symbol table '.dynsym' contains 6 entries:
Num:Value Size TypeBind Vis Ndx Name
0: 0 NOTYPE LOCAL DEFAULT UND
1:
So my previous comment isn't quite right.
For one thing, I *don't* think this affects DynamicUser=, only User= and
Group=. And https://sourceware.org/legacy-ml/libc-
help/2016-12/msg6.html says that nss modules are supposed to be ABI
compatible between releases but it appears that for
What appears to be going on here is that systemd is not restarted as
part of the upgrade of glibc so it is still running glibc 2.33. When
starting a service that does anything even slightly funky with users and
groups (so things that use DynamicUser= like systemd-resolved but also
things like
** Description changed:
+ Try this:
+
+ $ lxc launch ubuntu-daily:impish test-docker
+ $ lxc shell test-docker
+ # cat
13 matches
Mail list logo
