docker build的各种问题

系统需要打镜像包，然后部署到容器中运行
我在本地装了个docker desktop
没改什么配置就直接用起来，docker pull ubuntu，docker pull tomcat:7
然后就是docker buildx build -t 打包，然后docker save 一个tar包
很正常，但是默认是在系统盘，很快空间就没了
于是卸了之后想按攻略给装到其他盘里，各种失败，没办法，又装回到C盘来，赶紧得干活

这次问题来了，开始时候各种Pull失败，然后百度改了mirrors，总算可以跑起来了
可是今天在build的时候，死活又出问题
docker buildx build -t aaa:1.1 --platform linux/arm64 -o type=docker .
报错
ERROR: failed to solve: tomcat:7: failed to do request: Head "https://registry-1.docker.io/v2/library/tomcat/manifests/7": x509: certificate is valid for *.api-test.cfadevelop.com, *.app-test.cfadevelop.com, not registry-1.docker.io
百度了一下，说是镜像问题，可是按照方案改了，也还是不行
之前没改过配置也没出这种问题啊
青椒该怎么改

{
  {
  "builder": {
    "gc": {
      "defaultKeepStorage": "20GB",
      "enabled": true
    }
  },
  "debug": true,
  "experimental": false,
  "features": {
    "buildkit": true
  },
  "registry-mirrors": [
    "http://f1361db2.m.daocloud.io",
    "https://XXX.mirror.aliyuncs.com",
    "https://registry.docker-cn.com",
    "https://docker.mirrors.ustc.edu.cn"
  ]
}

这是我的buildx

dockfile内容

FROM tomcat:7
RUN apt-get update && apt-get install net-tools
COPY aaa.war /usr/local/tomcat/webapps/aaa.war

查的所有文章都是说修改配置为国内的镜像地址
我也修改了，道客的、阿里云的都加了
还是一样的错误
真是脑仁疼哦

2023-06-18编辑
今天用dig查了registry-1.docker.io之后，修改了host如下

44.205.64.79  registry-1.docker.io
34.205.13.154  registry-1.docker.io
3.216.34.172  registry-1.docker.io

修改了dns服务器为8.8.8.8
同步了系统时间
现在依然报错

ERROR: failed to solve: tomcat:7: failed to copy: httpReadSeeker: failed open: failed to do request: Get "https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/99/99e5503a8495c74905e0eff5c1b6224bade7d2a072cee6f58f3f72c35290726c/data?verify=1687049812-UPx1Cdc82%2FIjHaT7v%2BTMW2qq8Vk%3D%22: net/http: TLS handshake timeout

写回答
好问题 0 提建议
追加酬金
关注问题
分享
邀请回答
编辑收藏删除
收藏举报

2条回答默认最新

pushboy 2023-06-17 21:25

关注

咦，刚贴的日志怎么没了


[2023-06-17T13:06:13.425301500Z][com.docker.backend.exe][I] (520e1fa1) e0a54689-stats C->S VMDockerdAPI GET /vm/ram-cpu-usage
[2023-06-17T13:06:13.829527100Z][com.docker.backend.exe][I] (8439faba) 18f296a2-BackendAPI S<-C Go-http-client/1.1 GET /forwards/list
[2023-06-17T13:06:13.831390000Z][com.docker.backend.exe][I] (8439faba) 18f296a2-BackendAPI S->C Go-http-client/1.1 GET /forwards/list (1.8629ms): []
[2023-06-17T13:06:13.839456800Z][com.docker.backend.exe][I] (0c99cda8) 18f296a2-BackendAPI S<-C Go-http-client/1.1 GET /forwards/list
[2023-06-17T13:06:13.841120400Z][com.docker.backend.exe][I] (0c99cda8) 18f296a2-BackendAPI S->C Go-http-client/1.1 GET /forwards/list (1.6636ms): []
[2023-06-17T13:06:13.843622500Z][com.docker.backend.exe][I] (2381d429) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:13.844180200Z][com.docker.backend.exe][I] (2381d429) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerStartOthersLinux","count":1}
[2023-06-17T13:06:13.844744600Z][com.docker.backend.exe][I] (2381d429) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (1.1221ms): OK
[2023-06-17T13:06:13.876877800Z][com.docker.backend.exe][I] (caf0708c) 18f296a2-BackendAPI S<-C Go-http-client/1.1 GET /forwards/list
[2023-06-17T13:06:13.878915000Z][com.docker.backend.exe][I] (caf0708c) 18f296a2-BackendAPI S->C Go-http-client/1.1 GET /forwards/list (2.0372ms): []
[2023-06-17T13:06:13.880511700Z][com.docker.backend.exe][I] (f74d89b3) 18f296a2-BackendAPI S<-C Go-http-client/1.1 GET /forwards/list
[2023-06-17T13:06:13.882150200Z][com.docker.backend.exe][I] (f74d89b3) 18f296a2-BackendAPI S->C Go-http-client/1.1 GET /forwards/list (1.6385ms): []
[2023-06-17T13:06:14.379566700Z][com.docker.backend.exe][I] (78c79ebd) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:14.379967600Z][com.docker.backend.exe][I] vpnkitExposer.Add(62cabe633eb87470ad1f95cb9b56e35847f2efea70dd3e0dc19c8ef01e72c613, /buildx_buildkit_dwdb0, [])
[2023-06-17T13:06:14.380159600Z][com.docker.backend.exe][I] noopSharer.Add(62cabe633eb87470ad1f95cb9b56e35847f2efea70dd3e0dc19c8ef01e72c613, /buildx_buildkit_dwdb0, [])
[2023-06-17T13:06:14.380777500Z][com.docker.backend.exe][I] (78c79ebd) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerExecOthersLinux","count":1}
[2023-06-17T13:06:14.381329000Z][com.docker.backend.exe][I] (78c79ebd) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (1.7623ms): OK
[2023-06-17T13:06:14.391087300Z][com.docker.backend.exe][I] (e2bcb6a4) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:14.391713800Z][com.docker.backend.exe][I] (e2bcb6a4) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerStartOthersLinux","count":1}
[2023-06-17T13:06:14.392292100Z][com.docker.backend.exe][I] (e2bcb6a4) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (1.2048ms): OK
[2023-06-17T13:06:14.431661200Z][com.docker.backend.exe][I] (520e1fa1) e0a54689-stats C<-S 4c2718cb-VMDockerdAPI GET /vm/ram-cpu-usage (1.0053618s): {"cpuPercentage":9.529702970297029,"memAvailableBytes":7585728000,"memBytes":3760140000,"numCPU":8}
[2023-06-17T13:06:14.510515300Z][com.docker.backend.exe][I] (2e1c49f0) 18f296a2-BackendAPI S<-C Go-http-client/1.1 GET /forwards/list
[2023-06-17T13:06:14.512320300Z][com.docker.backend.exe][I] (2e1c49f0) 18f296a2-BackendAPI S->C Go-http-client/1.1 GET /forwards/list (1.805ms): []
[2023-06-17T13:06:14.667403900Z][com.docker.backend.exe][I] (f0678010) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:14.667961500Z][com.docker.backend.exe][I] (f0678010) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerExecOthersLinux","count":1}
[2023-06-17T13:06:14.668529500Z][com.docker.backend.exe][I] (f0678010) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (1.1256ms): OK
[2023-06-17T13:06:14.680187100Z][com.docker.backend.exe][I] (59c19eb3) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:14.681589900Z][com.docker.backend.exe][I] (59c19eb3) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerStartOthersLinux","count":1}
[2023-06-17T13:06:14.682477600Z][com.docker.backend.exe][I] (59c19eb3) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (2.2905ms): OK
[2023-06-17T13:06:14.884655200Z][com.docker.backend.exe][I] (f64b8d2f) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:14.885202600Z][com.docker.backend.exe][I] (f64b8d2f) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerExecOthersLinux","count":1}
[2023-06-17T13:06:14.885718900Z][com.docker.backend.exe][I] (f64b8d2f) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (1.0637ms): OK
[2023-06-17T13:06:14.895277200Z][com.docker.backend.exe][I] (0820861b) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:14.896009800Z][com.docker.backend.exe][I] (0820861b) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerStartOthersLinux","count":1}
[2023-06-17T13:06:14.896526100Z][com.docker.backend.exe][I] (0820861b) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (1.2489ms): OK
[2023-06-17T13:06:15.064695600Z][com.docker.backend.exe][I] (4391aaab) 18f296a2-BackendAPI S<-C Go-http-client/1.1 GET /forwards/list
[2023-06-17T13:06:15.066398500Z][com.docker.backend.exe][I] (4391aaab) 18f296a2-BackendAPI S->C Go-http-client/1.1 GET /forwards/list (1.7029ms): []
[2023-06-17T13:06:15.071216500Z][com.docker.backend.exe][I] (fe522ece) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:15.072400100Z][com.docker.backend.exe][I] (fe522ece) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerExecOthersLinux","count":1}
[2023-06-17T13:06:15.072995400Z][com.docker.backend.exe][I] (fe522ece) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (1.7789ms): OK
[2023-06-17T13:06:15.085598300Z][com.docker.backend.exe][I] (bfb7a9a2) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:15.087090500Z][com.docker.backend.exe][I] (bfb7a9a2) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerStartOthersLinux","count":1}
[2023-06-17T13:06:15.087625800Z][com.docker.backend.exe][I] (bfb7a9a2) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (2.0275ms): OK
[2023-06-17T13:06:15.239864000Z][com.docker.backend.exe][I] (477a6023) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:15.240866000Z][com.docker.backend.exe][I] (477a6023) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerExecOthersLinux","count":1}
[2023-06-17T13:06:15.241860100Z][com.docker.backend.exe][I] (477a6023) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (1.9961ms): OK
[2023-06-17T13:06:15.253863500Z][com.docker.backend.exe][I] (d9d9536a) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD POST /usage
[2023-06-17T13:06:15.253863500Z][com.docker.backend.exe][I] (d9d9536a) 18f296a2-BackendAPI S<-C 9d3da234-ProxyCMD bind: {"command":"containerStartOthersLinux","count":1}
[2023-06-17T13:06:15.254866000Z][com.docker.backend.exe][I] (d9d9536a) 18f296a2-BackendAPI S->C 9d3da234-ProxyCMD POST /usage (1.0025ms): OK
[2023-06-17T13:06:16.083600500Z][com.docker.backend.exe.gvisor/forwarder][I] 18.232.227.119:443 <- 192.168.65.3:58588: dialing
[2023-06-17T13:06:18.418403300Z][com.docker.backend.exe][I] (a771c0b5) e0a54689-stats C->S VMDockerdAPI GET /vm/ram-cpu-usage
[2023-06-17T13:06:19.425371300Z][com.docker.backend.exe][I] (a771c0b5) e0a54689-stats C<-S 4c2718cb-VMDockerdAPI GET /vm/ram-cpu-usage (1.006968s): {"cpuPercentage":0.1251564455569462,"memAvailableBytes":7585728000,"memBytes":3807416000,"numCPU":8}
[2023-06-17T13:06:19.832143200Z][com.docker.backend.exe.gvisor/forwarder][I] 3.218.162.19:443 <- 192.168.65.3:52802: dialing
[2023-06-17T13:06:23.420450300Z][com.docker.backend.exe][I] (696af5b8) e0a54689-stats C->S VMDockerdAPI GET /vm/ram-cpu-usage
[2023-06-17T13:06:23.580856300Z][com.docker.backend.exe.gvisor/forwarder][I] 23.22.155.84:443 <- 192.168.65.3:54082: dialing
[2023-06-17T13:06:24.427215900Z][com.docker.backend.exe][I] (696af5b8) e0a54689-stats C<-S 4c2718cb-VMDockerdAPI GET /vm/ram-cpu-usage (1.0067656s): {"cpuPercentage":0.1251564455569462,"memAvailableBytes":7585728000,"memBytes":3811448000,"numCPU":8}
[2023-06-17T13:06:25.008003100Z][com.docker.backend.exe.gvisor/forwarder][I] 18.232.227.119:443 <- 192.168.65.3:58588: dial failed: dial tcp 18.232.227.119:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[2023-06-17T13:06:27.329338000Z][com.docker.backend.exe.gvisor/forwarder][I] 3.94.35.164:443 <- 192.168.65.3:41104: dialing
[2023-06-17T13:06:27.558246400Z][com.docker.backend.exe.gvisor/forwarder][I] 3.94.35.164:443 <- 192.168.65.3:41104: dial succeeded, 4 active connections
[2023-06-17T13:06:28.043638300Z][com.docker.backend.exe.gvisor/forwarder][I] 3.94.35.164:443 <- 192.168.65.3:41104: closing, 3 active connections remaining
[2023-06-17T13:06:28.112003700Z][com.docker.backend.exe][I] (304fb161) f83ec199-CLIAPI S<-C Go-http-client/1.1 POST /usage
[2023-06-17T13:06:28.112549800Z][com.docker.backend.exe][I] (304fb161) f83ec199-CLIAPI S<-C Go-http-client/1.1 bind: {"command":"buildx build","context":"moby","source":"cli-buildx;docker-container","status":"failure"}
[2023-06-17T13:06:28.113081900Z][com.docker.backend.exe][I] (304fb161) f83ec199-CLIAPI S->C Go-http-client/1.1 POST /usage (1.0782ms): OK
[2023-06-17T13:06:28.425895800Z][com.docker.backend.exe][I] (89688800) e0a54689-stats C->S VMDockerdAPI GET /vm/ram-cpu-usage
[2023-06-17T13:06:29.430470600Z][com.docker.backend.exe][I] (89688800) e0a54689-stats C<-S 4c2718cb-VMDockerdAPI GET /vm/ram-cpu-usage (1.0045748s): {"memAvailableBytes":7585728000,"memBytes":3803100000,"numCPU":8}
[2023-06-17T13:06:33.411519700Z][com.docker.backend.exe][I] (46b9aa9b) e0a54689-stats C->S VMDockerdAPI GET /vm/ram-cpu-usage
[2023-06-17T13:06:34.416468100Z][com.docker.backend.exe][I] (46b9aa9b) e0a54689-stats C<-S 4c2718cb-VMDockerdAPI GET /vm/ram-cpu-usage (1.0049484s): {"cpuPercentage":0.125,"memAvailableBytes":7585728000,"memBytes":3810780000,"numCPU":8}
[2023-06-17T13:06:38.416144600Z][com.docker.backend.exe][I] (d31ef6cf) e0a54689-stats C->S VMDockerdAPI GET /vm/ram-cpu-usage
[2023-06-17T13:06:39.421168200Z][com.docker.backend.exe][I] (d31ef6cf) e0a54689-stats C<-S 4c2718cb-VMDockerdAPI GET /vm/ram-cpu-usage (1.0050236s): {"cpuPercentage":0.12531328320802004,"memAvailableBytes":7585728000,"memBytes":3809836000,"numCPU":8}
[2023-06-17T13:06:40.879590900Z][com.docker.backend.exe.gvisor/forwarder][I] 3.218.162.19:443 <- 192.168.65.3:52802: dial failed: dial tcp 3.218.162.19:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

本回答被题主选为最佳回答 , 对您是否有帮助呢?

查看更多回答(1条)

报告相同问题？

关注问题

docker build报错，dock build创建镜像报错 docker python 容器
2022-04-14 14:47

回答 2 已采纳解决了，进docker engine修改一下
诺兰Docker安装过程遇到各种问题 centos docker
2021-12-14 07:51

回答 5 已采纳卸载 docker 重新安装参考 docker https://www.runoob.com/docker/centos-docker-install.html
docker build问题大概意思是dockerfile找不到 docker 容器运维
2022-02-18 01:43

回答 4 已采纳我怀疑是你的 snap docker 镜像坏了，建议你删除snap docker镜像后在重新安装。不过你是ubuntu 操作系统吗?如果不是就别执行 snap 删除操作了，直接重装吧。 sudo s
经验之谈：八种Docker容器开发模式
2021-02-26 17:03

VidarHokstad在Docker使用方面非常有经验，尤其在没有数据丢失前提下，使用Docker创建可重复build上经验丰富，在本博客中，他总结了开发Docker容器的8种模式。Docker现在成了我最喜欢的工具，在本文中，我将概述一些...
docker 部署nginx 问题目录不同步 docker linux 运维
2022-08-08 18:13

回答 1 已采纳 /etc/nginx:/opt/nginx 目录权限有没问题？
docker被挖矿问题 docker 容器服务器
2022-01-05 10:58

回答 1 已采纳 1.信息太少，无法判断是如何感染的，至少从目前已知信息来看，是从容器感染还是服务器感染尚不能确定。说下常见的挂马方式： - web防火墙开放了违规端口，一般web防火墙（网络安全组）需要什么开通
docker-android-build:提供Android开发和构建环境的Android Dockerfile
2021-05-18 05:26

Android构建Dockerfile 提供了Android开发和构建环境的Android Dockerfile。该图像包含运行测试和构建基于Gradle的Android项目所需的所有软件包。... docker pull lukin0110/android-build 跑步 do
docker-compose build后出现错误 c++ docker
2022-10-06 10:15

回答 1 已采纳不知道你这个问题是否已经解决, 如果还没有解决的话: 请看👉 ：记一次运行 docker-compose 命令报错修复如果你已经解决了该问题, 非常希望你能够分享一下解决方案, 写成博客, 将相关
docker容器启动问题报端口占用 docker linux 容器
2023-01-29 22:23

回答 4 已采纳你不要慌，你现在看我下面的讲解就明白了你首先要知道 docker ps 和 docker ps -a的区别，不要看百度那些瞎几X抄来超区的， docker ps -a 包括活着的也包括异常失败的，所以
docker运行权限问题 docker linux
2022-01-25 10:22

回答 2 已采纳你尝试一下，将挂载的卷的目录，赋予 docker这用户组的权限。因为现在思考有点反了过来，还有，只有这个镜像是这样吗？好奇你这镜像是如何弄出来的，好奇你的 dockerfile
砖：基于Docker的简单monorepo构建工具
2021-02-25 08:00

brick是用于构建和部署monorepos的工具，并且在内部使用。它使用docker（buildkit）作为构建引擎。安装确保已安装docker，然后运行： python3 setup.py install 发展 pip3 install -e . 这将创建一个符号链接，...
docker卷挂载问题 docker
2022-06-24 17:25

回答 1 已采纳 Dockfile的挂载本身就是只能挂匿名，你在Dockerfile写相当于多路径但是都是匿名挂载
vscode-golang-docker:在Docker容器内进行开发环境
2021-05-12 21:44

vscode-golang-docker是Docker容器内的Go开发环境。它由Visual Studio Code和各种扩展组成，可帮助您编写，构建，测试和调试Go应用程序。它还将通过使用linters和其他支持工具来帮助您编写自己的shell脚本，...
dockerized-cli:使用Docker的容器化开发环境
2021-05-03 14:24

轻松地对您的构建/开发环境进行Docker化，并在其中无缝运行命令。 dockerized是一种用于在容器中无缝执行命令的工具。它会处理所有细节，因此您可以像在计算机上运行命令一样在容器中运行命令-只需在带有...
没有解决我的问题, 去提问

问题事件

关注

码龄粉丝数原力等级 --

被采纳

被点赞

采纳率
系统已结题 7月2日
关注

码龄粉丝数原力等级 --

被采纳

被点赞

采纳率
已采纳回答 6月24日
关注

码龄粉丝数原力等级 --

被采纳

被点赞

采纳率
修改了问题 6月18日
关注

码龄粉丝数原力等级 --

被采纳

被点赞

采纳率
修改了问题 6月17日
展开全部

悬赏问题

¥15 c语言怎么用printf（“\b \b”）与getch（）实现黑框里写入与删除？
¥20 怎么用dlib库的算法识别小麦病虫害
¥15 华为ensp模拟器中S5700交换机在配置过程中老是反复重启
¥15 java写代码遇到问题，求帮助
¥15 uniapp uview http 如何实现统一的请求异常信息提示？
¥15 有了解d3和topogram.js库的吗？有偿请教
¥100 任意维数的K均值聚类
¥15 stamps做sbas-insar，时序沉降图怎么画
¥15 买了个传感器，根据商家发的代码和步骤使用但是代码报错了不会改，有没有人可以看看
¥15 关于#Java#的问题，如何解决？

docker build的各种问题

2条回答 默认 最新

问题事件

悬赏问题

2条回答默认最新