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 v2 0/4] Update docker-moby to v25.0.9
Date: Thu, 26 Feb 2026 13:21:05 -0500	[thread overview]
Message-ID: <aaCPESlDm0dhwBUy@gmail.com> (raw)
In-Reply-To: <20260223-upstream-update-docker-moby-v2-0-5bc0d679d988@non.se.com>

merged.

Bruce

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

> This patch suite updates docker-moby to version v25.0.9 and
> removes the patches that were backported upstream for this release.
> 
> Note: 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>
> ---
> Changes in v2:
> - Revert ec01a803 adding CVE patches backported upstream
> - Link to v1: https://lists.yoctoproject.org/g/meta-virtualization/message/9591
> 
> ---
> F�lix Pi�dallu (4):
>       Revert "docker-moby: Security fix for CVE-2024-41110"
>       docker-moby: Update libnetwork
>       docker-moby: Update docker cli
>       docker-moby: Update to v25.0.9
> 
>  recipes-containers/docker/docker-moby_git.bb       |  13 +-
>  .../docker/files/CVE-2024-29018.patch              | 344 ---------------------
>  .../docker/files/CVE-2024-36620.patch              |  39 ---
>  .../docker/files/CVE-2024-36621.patch              |  82 -----
>  .../docker/files/CVE-2024-41110_1.patch            | 177 -----------
>  .../docker/files/CVE-2024-41110_2.patch            |  99 ------
>  6 files changed, 4 insertions(+), 750 deletions(-)
> ---
> base-commit: 78abd77b8695705e6e55266745c838bb665486de
> 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 (#9606): https://lists.yoctoproject.org/g/meta-virtualization/message/9606
> Mute This Topic: https://lists.yoctoproject.org/mt/117959928/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-26 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 16:35 [PATCH v2 0/4] Update docker-moby to v25.0.9 felix
2026-02-23 16:35 ` [PATCH v2 1/4] Revert "docker-moby: Security fix for CVE-2024-41110" felix
2026-02-23 16:35 ` [PATCH v2 2/4] docker-moby: Update libnetwork felix
2026-02-23 16:35 ` [PATCH v2 3/4] docker-moby: Update docker cli felix
2026-02-23 16:35 ` [PATCH v2 4/4] docker-moby: Update to v25.0.9 felix
2026-02-26 18:21 ` 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=aaCPESlDm0dhwBUy@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