podman build

首先检查 podman build -t lontronix/devcade . 使用的容器构建定义，尤其是基础镜像 python:3.8-buster 和 requirements.txt 安装步骤。重新运行构建以确认 Debian 仓库失败，然后验证更新后的构建能在干净的 clone 上成功完成。

Running

podman build -t lontronix/devcade .

failed with the output:

STEP 1/8: FROM docker.io/python:3.8-buster
Trying to pull docker.io/library/python:3.8-buster...
Getting image source signatures
Copying blob 819d305a9b22 done   |
Copying blob ac8bb7e1a323 done   |
Copying blob b1e7e053c9f6 done   |
Copying blob a2e1e233599c done   |
Copying blob 3b1c264c0ad4 done   |
Copying blob 0ebfe287e976 done   |
Copying blob a11e135762f0 done   |
Copying blob 5e4e21ea7d04 done   |
Copying config 406c715302 done   |
Writing manifest to image destination
STEP 2/8: LABEL maintainer="Andrew Simonson <asimonson1125@gmail.com>"
--> a6bb08414399
STEP 3/8: WORKDIR /app
--> d7cee96ad7b9
STEP 4/8: COPY ./requirements.txt requirements.txt
--> 67b6a39ad509
STEP 5/8: RUN apt-get -yq update &&     pip install --no-cache-dir -r requirements.txt
Ign:1 http://deb.debian.org/debian buster InRelease
Ign:2 http://deb.debian.org/debian-security buster/updates InRelease
Ign:3 http://deb.debian.org/debian buster-updates InRelease
Err:4 http://deb.debian.org/debian buster Release
  404  Not Found [IP: 2a04:4e42:3d::644 80]
Err:5 http://deb.debian.org/debian-security buster/updates Release
  404  Not Found [IP: 2a04:4e42:3d::644 80]
Err:6 http://deb.debian.org/debian buster-updates Release
  404  Not Found [IP: 2a04:4e42:3d::644 80]
Reading package lists...
E: The repository 'http://deb.debian.org/debian buster Release' does not have a Release file.
E: The repository 'http://deb.debian.org/debian-security buster/updates Release' does not have a Release file.
E: The repository 'http://deb.debian.org/debian buster-updates Release' does not have a Release file.
Error: building at STEP "RUN apt-get -yq update &&     pip install --no-cache-dir -r requirements.txt": while running runtime: exit status 100

This was done on a clean git clone on the main branch, on arch.
This is most likely due to the main website deb.debian.org not hosting buster and related files anymore.
My best guess on fixes is to change the url to a mirror that has the files or update the pod to use a new version of debian