Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#995191: Please backport "clone3" syscall workaround
129 views
Skip to first unread message
Shengjing Zhu
Sep 27, 2021, 2:30:04 PM9/27/21
to
Package: docker.io
Version: 20.10.8+dfsg1-1
Severity: important
X-Debbugs-Cc: zh...@debian.org
Control: found -1 20.10.5+dfsg1-1+b5
When the glibc in container image is bumped to 2.34, it uses "clone3" syscall,
which is not supported in docker's seccomp policy.
Bullseye should be fixed as well.
Error:
docker run --rm -it registry.fedoraproject.org/fedora:rawhide curl google.com
curl: (6) getaddrinfo() thread failed to start
Related links:
https://github.com/moby/moby/issues/42680
https://github.com/moby/moby/pull/42836
https://bugs.launchpad.net/cloud-images/+bug/1943049
Version: 20.10.8+dfsg1-1
Severity: important
X-Debbugs-Cc: zh...@debian.org
Control: found -1 20.10.5+dfsg1-1+b5
When the glibc in container image is bumped to 2.34, it uses "clone3" syscall,
which is not supported in docker's seccomp policy.
Bullseye should be fixed as well.
Error:
docker run --rm -it registry.fedoraproject.org/fedora:rawhide curl google.com
curl: (6) getaddrinfo() thread failed to start
Related links:
https://github.com/moby/moby/issues/42680
https://github.com/moby/moby/pull/42836
https://bugs.launchpad.net/cloud-images/+bug/1943049
0 new messages