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-dev netcat -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-dev netcat -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.
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).
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/d
docker镜像无法删除，通过 docker images 查看镜像明明存在就是删除不了。
删除提示：Error：No such image：xxxxxxx
具体截图内容如下：
解决方法
进入目录：
cd /var/lib/docker/image/overlay2/imagedb/content/sha256
该目录即为 docker 中的所有镜像文件（以shar256加密方式加密后的镜像文件），我们通过 ll 查看一下：
删哪个呢？别慌，docker images 中的 IMAGE ID 就可以确定镜像文件了。
觉得不确定的话，还可以通过文件大小查看一下：stat + 文件名
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
通过 service docker restart 尝试没有变化, 查看 docker 的日志 tail -5f /var/log/upstart/docker.log 发现
time=2017-04-
查阅各种资料，很多种说法，解决方案，有加RUN apt clean的，有说是DNS问题，修改docker配置的，但是我的都解决不了，然后，这次经历再次让我见识到了“重启大法”之功效。下面介绍下重启思路：
1- 想着可能是网络问题，首先尝试重启电脑；重启后，无效；
2- 那就可能是本机docker问题，重启docker；无效；
3- emm...可能的确是配置存在问题，我升级下docker试试；升级，重启，无效；
4- 盯着Pycharm看了半天，重启下P
[root@iZ2zeczvvb79boy368xppwZ ~]# cat /etc/redhat-release
CentOS Linux release 8.1.1911 (Core)
docker pull elasticsearch:6.4.0
修改虚拟机内存（貌似没有效果）
sysctl -w vm.max_map_count=262144
使用docker run命令跑容器
docker run -p 9200:9200 -p 9300:9300 --nam
相信了解过docker remote API的同学对2375端口都不陌生了，2375是docker远程操控的默认端口，通过这个端口可以直接对远程的docker daemon进行操作。
当$HOST主机以docker daemon -H=0.0.0.0:2375方式启动daemon时，可以在外部机器对$HOST的docker daemon进行直接操作：
docker -H tcp://$HOST:2375 ps
好，说说如何“入侵”，怎么通过这个端口入侵宿主机呢？
这个应该要从几个点说起吧：
1. docker对user namespace没有做隔离，也就是说，容器内部的root用户就是宿主机
docker-ce安装时出现错误：
dpkg: error processing package docker-ce (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned
---> Running in 05393fa6f242
Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB]
Err:1 http://ports.ubuntu.com/ubunt
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional pack
windows环境下一键搭建大数据开发环境，Java+hadoop+hbase+elasticsearch+apache-tomcat，对上海出租车历史数据进行了分析并做了轨迹数据可视化展现
浩哥——大数据+Python:
