Unable to build on Raspberry Pi 4

[ShaunLWM]

Previously I had warrior working on a vmware and the trouble was that it had to be shut down when I am off to bed. Now that I've got a RPI 4, I can keep it running 24/7. However when trying to build for RPI, there seemed to have some error while running sudo apt-get update in the Dockerfile.

Step 3/18 : RUN apt-get update
 ---> Running in 8dbb1fd1f43f
Get:1 http://deb.debian.org/debian sid InRelease [153 kB]
Err:1 http://deb.debian.org/debian sid InRelease
  At least one invalid signature was encountered.
Reading package lists...
W: GPG error: http://deb.debian.org/debian sid InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian sid InRelease' is not signed.
The command '/bin/sh -c apt-get update' returned a non-zero code: 100

Looking into debuerreotype/docker-debian-artifacts#101 which seemed to have the same error,

RPI version
Linux localhost 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l GNU/Linux
Docker
Docker version 20.10.2, build 2291f61
As of now, they seemed to have come to a conclusion that it's some building issues
docker-library/docker#260
djmaze/librespot-snapserver#7

May I know if there's any workaround on this end? Thank you!

[janpaul123]

Using FROM arm32v5/debian:stable-slim instead of FROM arm32v5/debian:sid-slim at the top of Dockerfile.raspberry fixed it for me.

[13rac1]

@janpaul123 Confirmed this solves the build issue.

Should this change be PR'd?

[LegendEffects]

Can confirm this allows the dockerfile to build but I had issues relating to #42 with none of the proposed solutions working.

[edofullin]

It seems to be a bigger issue, I've encountered it in other projects as well.

Updating libseccomp2_2 on the host seems to solve it, but I still get errors related to #42 with the Yahoo Answers project

[edofullin]

It seems like the dockerfile for the raspberry pi has not been updated for over 2 years and it no longer works (also it builds the image for armel insted of armhf)

However you can use the new Dockerfile for x86 for armhf as well, you just have to build wget-lua and grab-base-df for the new architecture.

Then you can just build this image from Dockerfile and it seems to work fine.

[TomGlass]

#56

[ramazansancar]

I have the same problem on Raspberry pi 4.
Is there a solution for this?

[TheTechRobo]

No: see #56