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 the ubuntu docker 
image:
"date -s" requires --privileged (which isn't available in docker build)
hwclock, which doesn't work on raspberry pi:

root@8f7355a71bca:/# hwclock --verbose
hwclock from util-linux 2.34
System Time: 0.-00001
Trying to open: /dev/rtc0
Trying to open: /dev/rtc
Trying to open: /dev/misc/rtc
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.

other means like ntp don't work because they aren't preinstalled and
cannot be installed because apt-get doesn't work (which is the topic of
this bugreport)

I was also not able to update libseccomp2, because wget and curl aren't
preinstalled and cannot be installed either, because apt-get doesn't
work.

-- 
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 docker arm container 20.04

Status in libseccomp package in Ubuntu:
  Confirmed

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

Reply via email to