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
4 matches
Mail list logo