Yocto Meta Virtualization
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: felix@piedallu.me
Cc: meta-virtualization@lists.yoctoproject.org,
	"Félix Piédallu" <felix.piedallu@non.se.com>,
	pascal.eberhard@se.com
Subject: Re: [meta-virtualization] [PATCH 0/3] Update docker-moby to v25.0.9
Date: Mon, 23 Feb 2026 03:58:11 +0000	[thread overview]
Message-ID: <aZvQUy2lluwbVT8f@gmail.com> (raw)
In-Reply-To: <20260216-upstream-update-docker-moby-v1-0-8ddcc5b7ff63@non.se.com>

I merged a set of CVE fixes to docker, and this no
longer applies.

It isn't that I can't fix the reject, it is that
it should be double checked to ensure that those
CVE fixes aren't duplicated in this minor bump or
cause other issues.

Can you send a new version once that check is done ?

Bruce

In message: [meta-virtualization] [PATCH 0/3] Update docker-moby to v25.0.9
on 16/02/2026 felix via lists.yoctoproject.org wrote:

> This patch updates docker-moby to version v25.0.9.
> 
> This is not the latest release of the v25.0 branch but the latest
> supporting Go 1.22, provided in oe-core scarthgap.
> Updating to newer releases will require updating go to 1.23.
> 
> Signed-off-by: F�lix Pi�dallu <felix.piedallu@non.se.com>
> ---
> F�lix Pi�dallu (3):
>       docker-moby: Update libnetwork
>       docker-moby: Update docker cli
>       docker-moby: Update to v25.0.9
> 
>  recipes-containers/docker/docker-moby_git.bb       |  11 +-
>  .../docker/files/CVE-2024-29018.patch              | 344 ---------------------
>  .../docker/files/CVE-2024-36620.patch              |  39 ---
>  .../docker/files/CVE-2024-36621.patch              |  82 -----
>  4 files changed, 4 insertions(+), 472 deletions(-)
> ---
> base-commit: 8b1543e121deda2445f80f74d85c10316d5b31f4
> change-id: 20260216-upstream-update-docker-moby-d0826db5916b
> 
> Best regards,
> -- 
> F�lix Pi�dallu <felix.piedallu@non.se.com>
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#9591): https://lists.yoctoproject.org/g/meta-virtualization/message/9591
> Mute This Topic: https://lists.yoctoproject.org/mt/117842532/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



      parent reply	other threads:[~2026-02-23  3:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 17:16 [PATCH 0/3] Update docker-moby to v25.0.9 felix
2026-02-16 17:16 ` [PATCH 1/3] docker-moby: Update libnetwork felix
2026-02-16 17:16 ` [PATCH 2/3] docker-moby: Update docker cli felix
2026-02-16 17:16 ` [PATCH 3/3] docker-moby: Update to v25.0.9 felix
2026-02-16 17:21 ` [meta-virtualization] [PATCH 0/3] Update docker-moby " Bruce Ashfield
2026-02-17  9:29   ` felix
2026-02-17 13:31     ` [meta-virtualization] " Bruce Ashfield
2026-02-17 13:59       ` felix
2026-02-23  3:58 ` Bruce Ashfield [this message]

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=aZvQUy2lluwbVT8f@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=felix.piedallu@non.se.com \
    --cc=felix@piedallu.me \
    --cc=meta-virtualization@lists.yoctoproject.org \
    --cc=pascal.eberhard@se.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox