> I confirm that this also affects Noble.
Thanks! Oracular and Noble are at the same version of libseccomp then, so I'll mark those tasks as still open.
> ...but `docker build` always uses the build-in/default profile, so it's a limited workaround.
Can Docker be fixed upstream instead, such that it works correctly with older libseccomp versions?
The instructions from the Test Plan led me to https://download.docker.com/linux/ubuntu/dists/noble/pool/stable/amd64/docker-ce-cli_26.1.4-1~ubuntu.24.04~noble_amd64.deb, which ships /usr/bin/docker, but that dynamic executable only uses libc. How is it accessing libseccomp dynamically, if at all? Is is using dlopen?
> I confirm that this also affects Noble.
Thanks! Oracular and Noble are at the same version of libseccomp then, so I'll mark those tasks as still open.
> ...but `docker build` always uses the build-in/default profile, so it's a limited workaround.
Can Docker be fixed upstream instead, such that it works correctly with older libseccomp versions?
The instructions from the Test Plan led me to https:/ /download. docker. com/linux/ ubuntu/ dists/noble/ pool/stable/ amd64/docker- ce-cli_ 26.1.4- 1~ubuntu. 24.04~noble_ amd64.deb, which ships /usr/bin/docker, but that dynamic executable only uses libc. How is it accessing libseccomp dynamically, if at all? Is is using dlopen?