From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: docker-image-debian-all-test-cross errors
Date: Mon, 6 Jul 2026 09:34:09 +0100 [thread overview]
Message-ID: <aktogcyff5Xinh5X@redhat.com> (raw)
In-Reply-To: <f5df268a-cc86-4a8a-aa5b-91c005244a2a@linaro.org>
On Sat, Jul 04, 2026 at 09:41:34PM -0700, Richard Henderson wrote:
> On 7/4/26 14:41, Mark Cave-Ayland wrote:
> > On 04/07/2026 22:20, Richard Henderson wrote:
> >
> > > Has anyone else been seeing
> > >
> > > Error: Failed to fetch
> > > http://deb.debian.org/debian/pool/main/d/dpkg/libdpkg-
> > > perl_1.22.21_all.deb 404 Not Found [IP: 151.101.22.132 80]
> > > Error: Failed to fetch
> > > http://deb.debian.org/debian/pool/main/d/dpkg/dpkg-
> > > dev_1.22.21_all.deb 404 Not Found [IP: 151.101.22.132 80]
> > > Error: Failed to fetch
> > > http://deb.debian.org/debian/pool/main/p/python3.13/
> > > libpython3.13_3.13.5-2_amd64.deb 404 Not Found [IP: 151.101.22.132
> > > 80]
> > > Error: Failed to fetch
> > > http://deb.debian.org/debian/pool/main/g/glibc/libc6-
> > > i386_2.41-12_amd64.deb 404 Not Found [IP: 151.101.22.132 80]
> > > Error: Unable to fetch some archives, maybe run apt-get update or try with --fix- missing?
> > > Error: building at STEP "RUN DEBIAN_FRONTEND=noninteractive
> > > eatmydata apt install - y --no-install-recommends clang
> > > dpkg-dev gdb-multiarch libclang-rt-dev": while running runtime:
> > > exit status 100
> > > make: *** [/home/rth/qemu/src/tests/docker/Makefile.include:43:
> > > docker-image-debian- all-test-cross] Error 100
> > >
> > > This has been consistently failing for me for a couple of weeks...
> > >
> > > r~
> >
> > I wonder if docker build has cached the existing layers, and since
> > apt-get update only runs in the first part of the Dockerfile then the
> > subsequent layers try to access an old base image?
> >
> > Does running "docker builder prune" (possibly with --all) help at all?
> > That should purge the cache and force docker to rebuild all the layers
> > again.
>
> No, it doesn't.
Note QEMU will preferentially to use 'podman' if both docker and
podman are installed. So 'docker builder prune' might be purging
the wrong cache. Try 'podman builder prune', or manually run
"podman pull docker.io/library/debian:13-slim" to force refresh
the base image.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-07-06 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 21:20 docker-image-debian-all-test-cross errors Richard Henderson
2026-07-04 21:41 ` Mark Cave-Ayland
2026-07-05 4:41 ` Richard Henderson
2026-07-06 8:34 ` Daniel P. Berrangé [this message]
2026-07-06 22:06 ` Richard Henderson
2026-07-05 9:07 ` Michael Tokarev
2026-07-05 21:14 ` Mark Cave-Ayland
2026-07-06 8:35 ` Alex Bennée
2026-07-06 22:28 ` Pierrick Bouvier
2026-07-07 9:29 ` Alex Bennée
2026-07-07 16:34 ` Pierrick Bouvier
2026-07-07 21:48 ` Pierrick Bouvier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aktogcyff5Xinh5X@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.