From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, mark.cave-ayland@ilande.co.uk,
richard.henderson@linaro.org,
"Alex Bennée" <alex.bennee@linaro.org>,
mjt@tls.msk.ru
Subject: Re: [PATCH 2/4] tests/docker/dockerfiles/ubuntu2404.docker: add missing apt update
Date: Wed, 8 Jul 2026 09:19:01 +0100 [thread overview]
Message-ID: <ak4H9Tn-t5rRH3oJ@redhat.com> (raw)
In-Reply-To: <20260707214655.1138626-3-pierrick.bouvier@oss.qualcomm.com>
On Tue, Jul 07, 2026 at 02:46:53PM -0700, Pierrick Bouvier wrote:
> RUN statements should always use apt update && apt install together:
> https://docs.docker.com/build/building/best-practices/#apt-get
>
> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
> ---
> tests/docker/dockerfiles/ubuntu2404.docker | 3 ++-
> tests/lcitool/refresh | 3 ++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/tests/docker/dockerfiles/ubuntu2404.docker b/tests/docker/dockerfiles/ubuntu2404.docker
> index 26bc2dd94f4..27992e34fd9 100644
> --- a/tests/docker/dockerfiles/ubuntu2404.docker
> +++ b/tests/docker/dockerfiles/ubuntu2404.docker
> @@ -160,7 +160,8 @@ ENV RUSTC=/usr/bin/rustc-1.83
> ENV RUSTDOC=/usr/bin/rustdoc-1.83
> ENV CARGO_HOME=/usr/local/cargo
> ENV PATH=$CARGO_HOME/bin:$PATH
> -RUN DEBIAN_FRONTEND=noninteractive eatmydata \
> +RUN apt update && \
> + DEBIAN_FRONTEND=noninteractive eatmydata \
> apt install -y --no-install-recommends cargo
> RUN cargo install --locked bindgen-cli
> # As a final step configure the user (if env is defined)
> diff --git a/tests/lcitool/refresh b/tests/lcitool/refresh
> index 1fdd37440c9..bbbc6d3c46a 100755
> --- a/tests/lcitool/refresh
> +++ b/tests/lcitool/refresh
> @@ -157,7 +157,8 @@ ENV RUSTC=/usr/bin/rustc-1.83
> ENV RUSTDOC=/usr/bin/rustdoc-1.83
> ENV CARGO_HOME=/usr/local/cargo
> ENV PATH=$CARGO_HOME/bin:$PATH
> -RUN DEBIAN_FRONTEND=noninteractive eatmydata \
> +RUN apt update && \
> + DEBIAN_FRONTEND=noninteractive eatmydata \
> apt install -y --no-install-recommends cargo
> RUN cargo install --locked bindgen-cli
So lcitool already ran 'apt update' earlier, but if we're trying to
avoid caching issues, I guess running it again is needed. Should we
also run 'apt dist-upgrade' though, as already installed content in
the cached layer can be outdated.
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-08 8:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 21:46 [PATCH 0/4] tests/docker/dockerfiles: add missing apt update Pierrick Bouvier
2026-07-07 21:46 ` [PATCH 1/4] tests/lcitool/refresh: use raw string literal for trailers Pierrick Bouvier
2026-07-08 8:13 ` Daniel P. Berrangé
2026-07-08 15:56 ` Pierrick Bouvier
2026-07-07 21:46 ` [PATCH 2/4] tests/docker/dockerfiles/ubuntu2404.docker: add missing apt update Pierrick Bouvier
2026-07-08 8:19 ` Daniel P. Berrangé [this message]
2026-07-08 9:27 ` Michael Tokarev
2026-07-08 14:28 ` Philippe Mathieu-Daudé
2026-07-08 14:54 ` Michael Tokarev
2026-07-08 16:11 ` Pierrick Bouvier
2026-07-08 16:14 ` Pierrick Bouvier
2026-07-08 16:38 ` Pierrick Bouvier
2026-07-08 20:46 ` Philippe Mathieu-Daudé
2026-07-07 21:46 ` [PATCH 3/4] tests/docker/dockerfiles/debian.docker: " Pierrick Bouvier
2026-07-08 8:25 ` Daniel P. Berrangé
2026-07-07 21:46 ` [PATCH 4/4] tests/docker/dockerfiles/debian-all-test-cross.docker: " Pierrick Bouvier
2026-07-08 8:50 ` Daniel P. Berrangé
2026-07-10 5:13 ` [PATCH 0/4] tests/docker/dockerfiles: " 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=ak4H9Tn-t5rRH3oJ@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mjt@tls.msk.ru \
--cc=pierrick.bouvier@oss.qualcomm.com \
--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.