sonar icon indicating copy to clipboard operation
sonar copied to clipboard

Build on Pi3 fails

Open sulrich70 opened this issue 2 years ago • 6 comments

W: GPG error: http://security.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered. E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is not signed. W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signed. W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is not signed. W: GPG error: http://archive.raspbian.org/raspbian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://archive.raspbian.org/raspbian bullseye InRelease' is not signed. W: GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://archive.raspberrypi.org/debian bullseye InRelease' is not signed. The command '/bin/sh -c install_packages wget redis' returned a non-zero code: 100 ERROR: Service 'redis' failed to build : Build failed

sulrich70 avatar Nov 08 '21 23:11 sulrich70

I am getting the same problem. Only I am using a Raspberry pi 4 model b.

I don't think the hardware is the issue, iv'e been fighting trying to figure out why this isn't working. So, I had everything up and running and working fine using Bullseye and running it on the newer Kernels 5.10.x.x+

My external wifi adapter is not compatible with the newer kernels so I went back to Buster, did a fresh install got everything setup, then encountered this error.

Interestingly enough, I got it to build the 1st fresh run of

sudo curl -fsSL get.databat.io | sudo bash

it only reported that the celery.env file was not found. Created the env files and now when trying to run the aforementioned or even just running sudo docker-compose up -d I get the following output.

Building redis Sending build context to Docker daemon 60.42kB Step 1/5 : FROM balenalib/raspberrypi3 ---> c39f6e4279d5 Step 2/5 : EXPOSE 6379 ---> Using cache ---> 53fa8dc65724 Step 3/5 : RUN install_packages wget redis ---> Running in 6064573d3c9d W: GPG error: http://security.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered. E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is not signed. W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signed. W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is not signed. W: GPG error: http://archive.raspbian.org/raspbian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://archive.raspbian.org/raspbian bullseye InRelease' is not signed. W: GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://archive.raspberrypi.org/debian bullseye InRelease' is not signed. apt failed, retrying W: GPG error: http://security.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered. E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is not signed. W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signed. W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is not signed. W: GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://archive.raspberrypi.org/debian bullseye InRelease' is not signed. W: GPG error: http://archive.raspbian.org/raspbian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://archive.raspbian.org/raspbian bullseye InRelease' is not signed. apt failed, retrying W: GPG error: http://security.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered. E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is not signed. W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signed. W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is not signed. W: GPG error: http://archive.raspbian.org/raspbian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://archive.raspbian.org/raspbian bullseye InRelease' is not signed. W: GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://archive.raspberrypi.org/debian bullseye InRelease' is not signed. The command '/bin/sh -c install_packages wget redis' returned a non-zero code: 100 ERROR: Service 'redis' failed to build : Build failed

Seems odd that on Buster it is trying to get over to bullseye. Am I missing something? Why is it calling for Bullseye repos if I am running Buster and don't even have Bullseye repo's in my sources?

MrSlipicus avatar Jun 29 '22 17:06 MrSlipicus

So, I managed to get past the above mentioned issue. I am a relative noob but here is what I have figured, and hopefully it is helpful.

Seems that the dockerimage is built using predefined keys to access bullseye repo's. I navigated to home/pi/sonar/redis/Dockerfile

and I changed

FROM balenalib/raspberrypi3 to FROM balenalib/raspberrypi3:buster

atleast in my case, this got me a step further. However, I am now getting Celery errors trying to complete the build.

MrSlipicus avatar Jun 29 '22 18:06 MrSlipicus

celery_1 | ImportError: cannot import name 'task' from 'celery' (/usr/local/lib/python3.7/dist-packages/celery/init.py)

MrSlipicus avatar Jun 29 '22 18:06 MrSlipicus

"ERROR: Couldn't find env file: /home/pi/sonar/celery.env" on install with curl -fsSL get.databat.io | sudo bash

sulrich70 avatar Jan 06 '23 00:01 sulrich70

Are you running as the user "pi"? Recent versions of raspbian allows you to use a custom username but the installer assumes the user pi.

vpetersson avatar Jan 06 '23 08:01 vpetersson

Are you running as the user "pi"? Recent versions of raspbian allows you to use a custom username but the installer assumes the user pi.

Yep - running as pi

sulrich70 avatar Jan 06 '23 08:01 sulrich70