@lucaskanashiro I don't doubt the importance of fixing bug 1943049[*].
My concern is that doing so with the current fix will knowingly break
nvidia-container-runtime users. Of course, if this is due to a bug in
nvidia-container-runtime, they should fix that. But at this point
(AFAICT) there still seems to be a possibility that this is a docker
regression.
[*] Though, fwiw, I'm not able to reproduce bug 1943094 on either a freshly
installed focal or impish host (lxd VM) using an ubuntu:impish container
verified to include libc6 2.34-0ubuntu3. But maybe I missed some important step.
** Changed in: docker.io (Ubuntu)
Status: Invalid => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948361
Title:
docker.io - error adding seccomp filter rule for syscall clone3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1948361/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
