no, wait, that is a different error message. When I run unprivileged, I
get
Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease
At least one invalid signature was encountered.
Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease
At least one invalid signature was encounter
I have verified that the date is indeed the problem. When I run an
ubuntu container privileged, the container has the correct date and apt
update succeeds. But when I run the container privileged and set the
date to 1971, then I get that same error message from apt update.
Therefore, this bug is a
So now I manually downloaded libseccomp2_2.5.0-3_armhf.deb, copied it
into the container and tried to install it from there. This didn't work
either:
Step 7/27 : RUN dpkg --force-all -P libseccomp2
---> Running in bf8c3eba1b94
dpkg: libseccomp2:armhf: dependency problems, but removing anyway as y
I have also tried this on ubuntu:20.10, ubuntu:20.04 and ubuntu:18.04 and it
produces the same error there, too.
I think it is an issue with the system clock reporting Jan 1st 1970. The system
clock on the host system is correct though.
I could only find two ways to change the system clock in th
Bug is probably invalid, as this is a problem on the non-Ubuntu host?
** Package changed: apt (Ubuntu) => libseccomp (Ubuntu)
--
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/bu
Thanks Anthony for the workaround.
Unfortunately #Method 1 won't work when building a docker image as --privileged
is not available on build :( But can be a useful workaround in some cases.
Might try #Method 2 but i'm not really into doing a package mess on my stable
arm build server...
So i gu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/
The root cause of the problem [is in libseccomp
When][1]. The newer version fixes the problem, but it is not yet available in
Debian's stable repos. There are two way to fix this problem:
**Method 1**
Start the container with `--privileged`. This bypasses docker's security
measures, so it is not
8 matches
Mail list logo
