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
相关推荐
做个文艺程序员5 小时前
第1篇：K8s 核心概念精讲：Pod、Deployment、Service 与 Namespace——Java 开发者快速上手指南
java·云原生·容器·kubernetes·容器编排
一勺菠萝丶5 小时前
Docker Desktop 启动后容器自动启动怎么办？如何关闭容器自启动
运维·docker·容器
Plastic garden9 小时前
K8s（2）安装，集群
云原生·容器·kubernetes
刘马想放假10 小时前
Docker 容器导出与镜像导出深度技术解析：docker export vs docker save
docker·容器
爱就是恒久忍耐10 小时前
老Ubuntu安装podman 5.x版本
linux·ubuntu·podman
JP-Destiny11 小时前
docker-安装nacos
运维·docker·容器
奋斗的好青年11 小时前
Ubuntu 修复 GRUB 引导并找回 Windows 双系统启动项（NVMe + MBR 环境）
linux·windows·ubuntu
森森-曦11 小时前
在windows系统上制作启动ubuntu_22.04.5_desktop_amd64.iso启动盘
windows·ubuntu·启动盘
你是个什么橙11 小时前
Docker下载安装及服务
运维·docker·容器
开发者联盟league11 小时前
在ubuntu上安装harbor
linux·运维·ubuntu
热门推荐
01GitHub 镜像站点02Codex 下载安装指南：Windows 和 macOS 官方版下载03【AI】2026 年具身智能模型和世界模型总结042026 年 AI 编程工具终极横评：Cursor vs Claude Code vs Copilot vs Windsurf05Codex 桌面端更新后 Chrome 插件和 Computer Use 不可用，怎么排查和修复06【踩坑记录 | 第一篇】微软商店无法使用时，如何手动安装 OpenAI Codex？附`.msix`文件系统错误解决方法07CC-Switch 下载、安装与使用配置指南【2026.5.29】08Codex 接入 DeepSeek API 完整配置文档09CC-Switch & Claude 基于 Linux 服务器安装使用指南10裂开！ChatGPT 居然开始要手机号验证，附详细解决方法