Docker容器创建时，无法访问镜像源：Could not connect to archive.ubuntu.com:80

瞭望清晨2024-09-08 11:05

1.问题描述

当基于dockerfile创建容器时，遇到Could not connect to ...、Failed to fetch ...等异常时，大概原因是没有配置好容器创建所需的镜像源。这里以Ubuntu基础镜像源为例。

  • dockerfile内容
bash 复制代码 
FROM ubuntu
RUN apt update && apt install python3 -y && apt install python3-pip -y && apt install git -y && apt install vim -y && apt install curl -y && apt install wget -y && apt install unzip -y && apt install zip -y && apt install tree -y && apt install npm -y
CMD ["bash"]
  • dockerfile执行与异常提示
bash 复制代码 
$ docker build -f data/dockerfiles --tag my_test

Get:1 http://mirrors.tools.aliyun.com/ubuntu focal InRelease [265 kB]
Get:2 http://mirrors.tools.aliyun.com/ubuntu focal-updates InRelease [128 kB]
Get:3 http://mirrors.tools.aliyun.com/ubuntu focal-backports InRelease [128 kB]
此处省略......
Ign:33 http://archive.ubuntu.com/ubuntu noble InRelease
Ign:34 http://archive.ubuntu.com/ubuntu noble-updates InRelease
Ign:35 http://archive.ubuntu.com/ubuntu noble-backports InRelease
此处省略......
  Could not connect to archive.ubuntu.com:80 (185.125.190.81), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.82), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.81), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.82), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.83), connection timed out
Err:34 http://archive.ubuntu.com/ubuntu noble-updates InRelease
  Unable to connect to archive.ubuntu.com:80:
此处省略......
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/noble/InRelease  Could not connect to archive.ubuntu.com:80 (185.125.190.81), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.82), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.81), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.82), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.83), connection timed out
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/noble-updates/InRelease  Unable to connect to archive.ubuntu.com:80:
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/noble-backports/InRelease  Unable to connect to archive.ubuntu.com:80:
此处省略......

2.解决方案

本质上，是需要修改基于镜像文件创建的容器中的/etc/apt/sources.list文件，将该文件中的镜像源从官方源换成国内源。这里以Ubuntu基础镜像源为例，有如下两种可选方案实施。

2.1.从dockerfile添加命令修改（自动化、简单）

打开dockerfile，在FROM ...命令后添加镜像源修改命令即可，如下：

bash 复制代码 
FROM ubuntu
# 镜像源修改命令
RUN sed -i "s@http://.*archive.ubuntu.com@http://mirrors.tools.aliyun.com@g" /etc/apt/sources.list
RUN sed -i "s@http://.*security.ubuntu.com@http://mirrors.tools.aliyun.com@g" /etc/apt/sources.list
# 容器软件安装命令
RUN apt update && apt install python3 -y && apt install python3-pip -y && apt install git -y && apt install vim -y && apt install curl -y && apt install wget -y && apt install unzip -y && apt install zip -y && apt install tree -y && apt install npm -y
CMD ["bash"]

添加镜像源修改命令后，再次执行容器构建命令docker build -f data/dockerfiles --tag my_test，即可快速完成容器构建。

2.2.从创建启动的基础镜像容器修改（略微繁琐）

  • （1）创建启动基础镜像的容器

    bash 复制代码 
    $ docker run -it ubuntu /bin/bash

  • （2）进入容器命令行，然后手动修改sources.list文件

    shell 复制代码 
    $ vim /etc/apt/sources.list

# 官方sources.list文件内容
deb http://archive.ubuntu.com/ubuntu/ bionic main restricted
deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic universe
deb-src http://archive.ubuntu.com/ubuntu/ bionic universe
deb http://archive.ubuntu.com/ubuntu/ bionic-updates universe
deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates universe
deb http://archive.ubuntu.com/ubuntu/ bionic multiverse
deb-src http://archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted
deb-src http://security.ubuntu.com/ubuntu/ bionic-security main restricted
deb http://security.ubuntu.com/ubuntu/ bionic-security universe
deb-src http://security.ubuntu.com/ubuntu/ bionic-security universe
deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse
deb-src http://security.ubuntu.com/ubuntu/ bionic-security multiverse

    将上述官方sources.list文件内容修改为如下：

    sehll 复制代码 
    deb http://mirrors.tools.aliyun.com/ubuntu bionic main restricted
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic main restricted
deb http://mirrors.tools.aliyun.com/ubuntu bionic-updates main restricted
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic-updates main restricted
deb http://mirrors.tools.aliyun.com/ubuntu bionic universe
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic universe
deb http://mirrors.tools.aliyun.com/ubuntu bionic-updates universe
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic-updates universe
deb http://mirrors.tools.aliyun.com/ubuntu bionic multiverse
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic multiverse
deb http://mirrors.tools.aliyun.com/ubuntu bionic-updates multiverse
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic-updates multiverse
deb http://mirrors.tools.aliyun.com/ubuntu bionic-backports main restricted universe multiverse
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic-backports main restricted universe multiverse
deb http://mirrors.tools.aliyun.com/ubuntu bionic-security main restricted
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic-security main restricted
deb http://mirrors.tools.aliyun.com/ubuntu bionic-security universe
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic-security universe
deb http://mirrors.tools.aliyun.com/ubuntu bionic-security multiverse
deb-src http://mirrors.tools.aliyun.com/ubuntu bionic-security multiverse

    注意，重要事情说3遍：
    该步骤一定是在启动的基础镜像容器内部执行！！！
    该步骤一定是在启动的基础镜像容器内部执行！！！
    该步骤一定是在启动的基础镜像容器内部执行！！！

  • （3）在当前容器中，手动安装dockerfile中列出的其他软件包

    bash 复制代码 
    apt update && apt install python3 -y && apt install python3-pip -y && apt install git -y && apt install vim -y && apt install curl -y && apt install wget -y && apt install unzip -y && apt install zip -y && apt install tree -y && apt install npm -y
相关推荐
helloworddm19 分钟前
Orleans + Kubernetes + Istio 服务网格集成深度解析
容器·kubernetes·istio
小彭律师22 分钟前
Docker/K8s部署MySQL的创新实践与优化技巧大纲
mysql·docker·kubernetes
lastHertz24 分钟前
Docker 占用导致 C 盘空间不足的排查与解决
运维·docker·容器
专家大圣25 分钟前
Docker+Redis监控新方案：cpolar让远程管理“零配置”
网络·redis·docker·容器·内网穿透
chen_note4 小时前
Dockerfile及其部署镜像步骤
docker·容器·镜像·dockerfile
Jy_06225 小时前
K8s中，deployment 是如何从 yaml 文件最终部署成功 pod 的
云原生·容器·kubernetes
mobº5 小时前
K8s 集群环境搭建 - yaml 版本（一）
云原生·容器·kubernetes
终端行者5 小时前
K8s中部署Minio集群 如何部署minio集群
云原生·容器·kubernetes·1024程序员节
杨浦老苏10 小时前
开源云文件存储服务器MyDrive
docker·群晖·网盘
PellyKoo10 小时前
Docker容器中中文文件名显示乱码问题完美解决方案
运维·docker·容器
热门推荐
01BongoCat - 跨平台键盘猫动画工具02GitHub 镜像站点03UV安装并设置国内源04GitLab 零基础入门指南：从安装到项目管理全流程05Linux下V2Ray安装配置指南06NVIDIA显卡驱动、CUDA、cuDNN 和 TensorRT 版本匹配指南07jdk21下载、安装（Windows、Linux、macOS）08Labelme从安装到标注：零基础完整指南092025软件测试面试八股文（含答案+文档）10在VSCode配置Java开发环境的保姆级教程（适配各类AI编程IDE）