At least one invalid signature was encountered
Jun 19
I am trying to build and deploy microservices images to a single-node Kubernetes cluster running on my development machine using minikube. I am using the cloud-native microservices demo application Online Boutique by Google to understand the use of technologies like Kubernetes, Istio etc.
While following the installation process, and on running command skaffold run to build and deploy my application, I get some errors:
Step 10/11 : RUN apt-get -qq update && apt-get install -y --no-install-recommends curl
---> Running in 43d61232617c
W: GPG error: http://deb.debian.org/debian buster InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian buster InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian buster-updates InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian buster-updates InRelease' is not signed.
W: GPG error: http://security.debian.org/debian-security buster/updates InRelease: At least one invalid signature was encountered.
E: The repository 'http://security.debian.org/debian-security buster/updates InRelease' is not signed.
failed to build: couldn't build "loadgenerator": unable to stream build output: The command '/bin/sh -c apt-get -qq update && apt-get install -y --no-install-recommends curl' returned a non-zero code: 100
I receive these errors when trying to build loadgenerator. How can I resolve this issue?
docker
kubernetes1 answer
Accepted answer · original discussion
Jun 22
There are a few reasons why you encounter these errors:
There might be an issue with the existing cache and/or disc space. In order to fix it you need to clear the APT cache by executing:
sudo apt-get cleanandsudo apt-get update.The same goes with existing docker images. Execute:
docker image prune -fanddocker container prune -fin order to remove unused data and free disc space. Executingdocker image prune -fwill delete all the unused images. To delete some selective images of large size, rundocker imagesand identify the images you want to remove, and then rundocker rmi -f <IMAGE-ID1> <IMAGE-ID2> <IMAGE-ID3>.If you don't care about the security risks, you can try to run the
apt-getcommand with the--allow-unauthenticatedor--allow-insecure-repositoriesflag. According to the docs:Ignore if packages can't be authenticated and don't prompt about it. This can be useful while working with local repositories, but is a huge security risk if data authenticity isn't ensured in another way by the user itself.
0 question comments
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.