For the privileged/unprivileged issue mentioned in comment #6, these upstream comments appears to be pertinent, suggesting patches that may be worth backporting: https://github.com/moby/moby/issues/40734#issuecomment-614259072 https://github.com/moby/moby/issues/40734#issuecomment-680250761
As to the gpg errors in comment #8, I suspect those are unrelated. Those types of errors can crop up for a wide variety of reasons, including insufficient disk space, networking glitches, gpg problems, etc. all mostly unrelated to the package itself, so I would suggest looking to regular support channels for help there, for example see https://superuser.com/questions/1059346/apt-get-update-not-working- signing-verification-errors which suggests several solutions. If not, let us know. However, it's possible that the gpg error is hiding the earlier error, and potentially once its resolved the earlier error will come back. So I'll leave this issue open for now. ** Changed in: libseccomp (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on unprivileged docker arm container due to invalid gpg signature Status in libseccomp package in Ubuntu: Incomplete Bug description: Running `apt update` in a ubuntu:20.04 docker container on raspberry pi fails with GPG errors. Expected behaviour: Successfully update the system through `apt update` What happens instead: `Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease At least one invalid signature was encountered.` Complete log: https://pastebin.com/sggGJcY1 How to reproduce: On a Raspberry Pi 3b or 4b (and maybe others ?), run the following command: `docker run ubuntu:latest apt update` or more specifically: `docker run arm32v7/ubuntu:20.04 apt update` More information: I can reproduce the bug on the following host systems: * Raspberry Pi 3b running HypriotOS * Raspberry Pi 4b running Raspbian GNU/Linux 10 (buster) The problem does not happens on the following host system: * Raspberry Pi 3b running Arch Linux Arm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
