docker|docker出现GPG error: At least one invalid signature was encountered 相关问题及解决方法 docker|dockerfile|gpg|signature|erro

docker出现GPG error: At least one invalid signature was encountered 相关问题及解决方法。

W: GPG error: http://mirrors.tuna.tsinghua.edu.cn/debian buster InRelease: At least one invalid signature was encountered. E: The repository 'http://mirrors.tuna.tsinghua.edu.cn/debian buster InRelease' is not signed. W: GPG error: http://mirrors.tuna.tsinghua.edu.cn/debian buster-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://mirrors.tuna.tsinghua.edu.cn/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. ERROR: Service 'flake8' failed to build : The command '/bin/sh -c sed -i 's/deb.debian.org/mirrors.tuna.tsinghua.edu.cn/g' /etc/apt/sources.list && apt-get update&& apt-get install tzdata cron libboost-dev libboost-python-devnetcat -y && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

W: GPG error: http://mirrors.tuna.tsinghua.edu.cn/debian buster InRelease: At least one invalid signature was encountered. E: The repository 'http://mirrors.tuna.tsinghua.edu.cn/debian buster InRelease' is not signed. W: GPG error: http://mirrors.tuna.tsinghua.edu.cn/debian buster-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://mirrors.tuna.tsinghua.edu.cn/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. ERROR: Service 'autotest' failed to build : The command '/bin/sh -c sed -i 's/deb.debian.org/mirrors.tuna.tsinghua.edu.cn/g' /etc/apt/sources.list && apt-get update&& apt-get install tzdata cron libboost-dev libboost-python-devnetcat -y && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB] Get:2 http://deb.debian.org/debian buster InRelease [121 kB] Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB] Get:4 http://security.debian.org/debian-security buster/updates/main amd64 Packages [248 kB] Get:5 http://deb.debian.org/debian buster/main amd64 Packages [7906 kB] Get:6 http://deb.debian.org/debian buster-updates/main amd64 Packages [7856 B] Fetched 8401 kB in 4s (2021 kB/s)

解决方法：

docker image prune -a docker container prune -a docker system prune docker system df 之后再执行原来的命令。。。。

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 clean and sudo apt-get update.
The same goes with existing docker images. Execute: docker image prune -f and docker container prune -f in order to remove unused data and free disc space.
If you don’t care about the security risks, you can try to run the apt-get command with the --allow-unauthenticated or --allow-insecure-repositories flag. 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.
【docker|docker出现GPG error: At least one invalid signature was encountered 相关问题及解决方法】Finally, on MacOS, where Docker runs inside a dedicated VM, you may need to increase the disk available to Docker from the Docker Desktop application (Settings -> Resources -> Advanced -> Disk image size).