Microsoft MVP성태의 닷넷 이야기
글쓴 사람
정성태 (seongtaejeong at gmail.com)
홈페이지
첨부 파일
 

apt update 시 "The repository 'http://deb.debian.org/debian buster Release' does not have a Release file." 오류

이상하군요, (Visual Studio로 생성한) ASP.NET Core 프로젝트의 dockerfile에 추가한 "apt update" 명령어가 docker build 시 오류가 발생합니다. 단순하게 "sdk;3.1-buster" 이미지만으로도 apt update가 실패합니다.

c:\temp> type test.dockerfile
FROM mcr.microsoft.com/dotnet/core/sdk:3.1-buster
RUN apt-get update

c:\temp> docker build -f test.dockerfile -t test_dotnet_img .
[+] Building 10.8s (5/5) FINISHED                                                                  docker:desktop-linux
 => [internal] load build definition from test.dockerfile                                                          0.4s
 => => transferring dockerfile: 112B                                                                               0.0s
 => [internal] load metadata for mcr.microsoft.com/dotnet/core/sdk:3.1-buster                                      0.6s
 => [internal] load .dockerignore                                                                                  0.8s
 => => transferring context: 2B                                                                                    0.0s
 => CACHED [1/2] FROM mcr.microsoft.com/dotnet/core/sdk:3.1-buster@sha256:ed737e6920105e2a5cdcd13b9697e7973011e56  2.4s
 => => resolve mcr.microsoft.com/dotnet/core/sdk:3.1-buster@sha256:ed737e6920105e2a5cdcd13b9697e7973011e5619339ea  2.3s
 => ERROR [2/2] RUN apt-get update                                                                                 5.5s
------
 > [2/2] RUN apt-get update:
4.780 Ign:1 http://deb.debian.org/debian buster InRelease
4.788 Ign:2 http://deb.debian.org/debian-security buster/updates InRelease
4.794 Ign:3 http://deb.debian.org/debian buster-updates InRelease
4.801 Err:4 http://deb.debian.org/debian buster Release
4.801   404  Not Found [IP: 146.75.50.132 80]
4.815 Err:5 http://deb.debian.org/debian-security buster/updates Release
4.815   404  Not Found [IP: 146.75.50.132 80]
4.822 Err:6 http://deb.debian.org/debian buster-updates Release
4.822   404  Not Found [IP: 146.75.50.132 80]
5.067 Reading package lists...
5.078 E: The repository 'http://deb.debian.org/debian buster Release' does not have a Release file.
5.078 E: The repository 'http://deb.debian.org/debian-security buster/updates Release' does not have a Release file.
5.078 E: The repository 'http://deb.debian.org/debian buster-updates Release' does not have a Release file.
------
test.dockerfile:2
--------------------
   1 |     FROM mcr.microsoft.com/dotnet/core/sdk:3.1-buster
   2 | >>> RUN apt-get update
--------------------
ERROR: failed to solve: process "/bin/sh -c apt-get update" did not complete successfully: exit code: 100

View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/zkz3vs4wtw6bpiinp9don2xk5

사실 sdk;3.1-buster 이미지의 근간이 되는 debian:10 이미지로도 동일한 오류가 발생합니다.

c:\temp> type debian.dockerfile
FROM debian:10
RUN apt-get update

c:\temp> docker build -f debian.dockerfile -t test_debian_img .
[+] Building 29.4s (5/5) FINISHED                                                                  docker:desktop-linux
 => [internal] load build definition from debian.dockerfile                                                        0.3s
 => => transferring dockerfile: 78B                                                                                0.1s
 => [internal] load metadata for docker.io/library/debian:10                                                       3.1s
 => [internal] load .dockerignore                                                                                  0.3s
 => => transferring context: 2B                                                                                    0.0s
 => [1/2] FROM docker.io/library/debian:10@sha256:58ce6f1271ae1c8a2006ff7d3e54e9874d839f573d8009c20154ad0f2fb0a2  11.0s
 => => resolve docker.io/library/debian:10@sha256:58ce6f1271ae1c8a2006ff7d3e54e9874d839f573d8009c20154ad0f2fb0a22  0.4s
 => => sha256:3892befd2c3f36ceb247ba7d906de12601d69b806597e65c4c837cf3d93df119 50.66MB / 50.66MB                   6.2s
 => => extracting sha256:3892befd2c3f36ceb247ba7d906de12601d69b806597e65c4c837cf3d93df119                          3.4s
 => ERROR [2/2] RUN apt-get update                                                                                12.8s
------
 > [2/2] RUN apt-get update:
1.603 Ign:1 http://deb.debian.org/debian buster InRelease
1.610 Ign:2 http://deb.debian.org/debian-security buster/updates InRelease
1.618 Ign:3 http://deb.debian.org/debian buster-updates InRelease
1.624 Err:4 http://deb.debian.org/debian buster Release
1.624   404  Not Found [IP: 146.75.50.132 80]
1.634 Err:5 http://deb.debian.org/debian-security buster/updates Release
1.634   404  Not Found [IP: 146.75.50.132 80]
1.642 Err:6 http://deb.debian.org/debian buster-updates Release
1.642   404  Not Found [IP: 146.75.50.132 80]
1.646 Reading package lists...
1.654 E: The repository 'http://deb.debian.org/debian buster Release' does not have a Release file.
1.654 E: The repository 'http://deb.debian.org/debian-security buster/updates Release' does not have a Release file.
1.654 E: The repository 'http://deb.debian.org/debian buster-updates Release' does not have a Release file.
------
debian.dockerfile:2
--------------------
   1 |     FROM debian:10
   2 | >>> RUN apt-get update
--------------------
ERROR: failed to solve: process "/bin/sh -c apt-get update" did not complete successfully: exit code: 100

View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/yzh9f8knxns4twzcukxwrgma0

저도 이젠 유경험자도 보니 ^^ 원인을 대충 짐작할 수 있었는데요,

dockerfile - 구 버전의 .NET Core 이미지 사용 시 apt update 오류
; https://www.sysnet.pe.kr/2/0/13331

당시의 "stretch" 버전에 이어서 이제는 "buster" 버전이 지원 종료(EOL, End Of Life)가 되었기 때문입니다.
c:\temp> docker run -it --rm --name my_test test_debian_img /bin/bash
root@1434c0b6d1ec:/# cat /etc/apt/sources.list
# deb http://snapshot.debian.org/archive/debian/20221219T000000Z buster main
deb http://deb.debian.org/debian buster main
# deb http://snapshot.debian.org/archive/debian-security/20221219T000000Z buster/updates main
deb http://deb.debian.org/debian-security buster/updates main
# deb http://snapshot.debian.org/archive/debian/20221219T000000Z buster-updates main
deb http://deb.debian.org/debian buster-updates main

따라서, 이번에도 repo 주소를 archive 쪽으로 변경해 주면 됩니다.

c:\temp> type debian.dockerfile
FROM debian:10
RUN echo "deb http://archive.debian.org/debian buster main" > /etc/apt/sources.list
RUN apt-get update

c:\temp> docker build -f debian.dockerfile -t test_debian_img .




저렇게 archive 주소로 변경한 이후 apt install 명령어에서 procps 패키지 설치 시 새롭게 문제가 발생했습니다.

# apt install procps -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 procps : Depends: libncurses6 (>= 6) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

# apt install libncurses6 -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libncurses6 : Depends: libtinfo6 (= 6.1+20181013-2+deb10u2) but 6.1+20181013-2+deb10u5 is to be installed
               Recommends: libgpm2 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

여기서 근본적인 문제는 libncurses6가 정확히 6.1+20181013-2+deb10u2 버전에 의존적이라고 명시했다는 점입니다. 그래서 해당 구성 요소를 이렇게 설치하면 안 되고,

// 6.1+20181013-2+deb10u5 버전의 libtinfo6가 설치됨

# apt install libtinfo6 -y

정확히 버전까지 지정해야 하는데요, 아쉽게도 경고가 나옵니다.

# apt install libtinfo6=6.1+20181013-2+deb10u2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libfdisk1 libmount1 libsmartcols1
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  fdisk libncursesw6 mount sysvinit-utils util-linux
The following packages will be DOWNGRADED:
  libtinfo6
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  fdisk libncursesw6 (due to fdisk) mount util-linux (due to mount) sysvinit-utils
0 upgraded, 0 newly installed, 1 downgraded, 5 to remove and 0 not upgraded.
Need to get 325 kB of archives.
After this operation, 5897 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
 ?] Yes, do as I say!

사실 docker 이미지라면 fdisk 등의 도구가 필요 없을 테니 제거해도 무방할 것입니다. 어쨌든 저렇게 변경하면 이후 procps 설치까지 문제는 없습니다.

정리하면, procps 설치를 한다면 이렇게 dockerfile을 구성하면 됩니다.

FROM debian:10
RUN echo "deb http://archive.debian.org/debian buster main" > /etc/apt/sources.list

RUN apt update && apt upgrade -y

RUN echo "Yes, do as I say!" | apt install libtinfo6=6.1+20181013-2+deb10u2
RUN apt install libncurses6 -y
RUN apt install procps -y




[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]







[최초 등록일: ]
[최종 수정일: 9/1/2025]

Creative Commons License
이 저작물은 크리에이티브 커먼즈 코리아 저작자표시-비영리-변경금지 2.0 대한민국 라이센스에 따라 이용하실 수 있습니다.
by SeongTae Jeong, mailto:techsharer at outlook.com

비밀번호

댓글 작성자
 




... 46  47  48  49  [50]  51  52  53  54  55  56  57  58  59  60  ...
NoWriterDateCnt.TitleFile(s)
12778정성태8/12/202116907오류 유형: 755. PyCharm - "Manage Repositories"의 목록이 나오지 않는 문제
12777정성태8/12/202119197오류 유형: 754. Visual Studio - Input or output cannot be redirected because the specified file is invalid.
12776정성태8/12/202117284오류 유형: 753. gunicorn과 uwsgi 함께 사용 시 ERR_CONNECTION_REFUSED
12775정성태8/12/202131449스크립트: 22. 파이썬 - 윈도우 환경에서 개발한 Django 앱을 WSL 환경의 gunicorn을 이용해 실행
12774정성태8/11/202121416.NET Framework: 1087. C# - Collection 개체의 다중 스레드 접근 시 "Operations that change non-concurrent collections must have exclusive access" 예외 발생
12773정성태8/11/202120678개발 환경 구성: 595. PyCharm - WSL과 연동해 Django App을 윈도우에서 리눅스 대상으로 개발
12772정성태8/11/202120696스크립트: 21. 파이썬 - 윈도우 환경에서 개발한 Django 앱을 WSL 환경의 uwsgi를 이용해 실행 [1]
12771정성태8/11/202119472Windows: 196. "Microsoft Windows Subsystem for Linux Background Host" / "Vmmem"을 종료하는 방법
12770정성태8/11/202118751.NET Framework: 1086. C# - Windows Forms 응용 프로그램의 자식 컨트롤 부하파일 다운로드1
12769정성태8/11/202115545오류 유형: 752. Python - ImportError: No module named pip._internal.cli.main 두 번째 이야기
12768정성태8/10/202116824.NET Framework: 1085. .NET 6에 포함된 신규 BCL API [1]파일 다운로드1
12767정성태8/10/202117719오류 유형: 752. Python - ImportError: No module named pip._internal.cli.main
12766정성태8/9/202115928Java: 32. closing inbound before receiving peer's close_notify
12765정성태8/9/202118026Java: 31. Cannot load JDBC driver class 'org.mysql.jdbc.Driver'
12764정성태8/9/202156139Java: 30. XML document from ServletContext resource [/WEB-INF/applicationContext.xml] is invalid
12763정성태8/9/202120543Java: 29. java.lang.NullPointerException - com.mysql.jdbc.ConnectionImpl.getServerCharset
12762정성태8/8/202122673Java: 28. IntelliJ - Unable to open debugger port 오류
12761정성태8/8/202118898Java: 27. IntelliJ - java: package javax.inject does not exist [2]
12760정성태8/8/202114841개발 환경 구성: 594. 전용 "Command Prompt for ..." 단축 아이콘 만들기
12759정성태8/8/202121465Java: 26. IntelliJ + Spring Framework + 새로운 Controller 추가 [2]파일 다운로드1
12758정성태8/7/202121096오류 유형: 751. Error assembling WAR: webxml attribute is required (or pre-existing WEB-INF/web.xml if executing in update mode)
12757정성태8/7/202121649Java: 25. IntelliJ + Spring Framework 프로젝트 생성
12756정성태8/6/202118255.NET Framework: 1084. C# - .NET Core Web API 단위 테스트 방법 [1]파일 다운로드1
12755정성태8/5/202119824개발 환경 구성: 593. MSTest - 단위 테스트에 static/instance 유형의 private 멤버 접근 방법파일 다운로드1
12754정성태8/5/202120377오류 유형: 750. manage.py - Your project may not work properly until you apply the migrations for app(s): admin, auth, contenttypes, sessions.
12753정성태8/5/202121326오류 유형: 749. PyCharm - Error: Django is not importable in this environment
... 46  47  48  49  [50]  51  52  53  54  55  56  57  58  59  60  ...