From: Stefan Agner <stefan@agner.ch>
To: Christian Stewart <christian@aperture.us>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/1] package/containerd: bump version to v1.6.22
Date: Fri, 08 Sep 2023 01:23:06 +0200 [thread overview]
Message-ID: <b73fb293249bcf48f42ebaed0f78f1c1@agner.ch> (raw)
In-Reply-To: <20230727232235.449788-1-christian@aperture.us>
Hi Christian,
It seems that this version hangs at startup, at least when built with
Buildroot 2023.02.4.
Typically my systemd services just timeout. When I manually start
containerd it just doesn't reach the message "containerd successfully
booted in", which older version did.
I've tested v1.6.23 as well, it shows the same behavior. For now I
reverted to v1.6.21.
Have you seen this behavior?
Btw, on master, where we use Docker 24.0.x, shouldn't containerd be
upgraded to the 1.7.x series?
--
Stefan
On 2023-07-28 01:22, Christian Stewart via buildroot wrote:
> Bugfixes and updates.
>
> https://github.com/containerd/containerd/releases/tag/v1.6.22
>
> Signed-off-by: Christian Stewart <christian@aperture.us>
> ---
> package/containerd/containerd.hash | 2 +-
> package/containerd/containerd.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/containerd/containerd.hash
> b/package/containerd/containerd.hash
> index 345a7b16ff..8404675e30 100644
> --- a/package/containerd/containerd.hash
> +++ b/package/containerd/containerd.hash
> @@ -1,3 +1,3 @@
> # Computed locally
> -sha256
> 9452e95455d03a00d78ae0587595d0c18555bae7912068269efa25a724efe713
> containerd-1.6.21.tar.gz
> +sha256
> b109aceacc814d7a637ed94ba5ade829cd2642841d03e06971ef124fa3b86899
> containerd-1.6.22.tar.gz
> sha256
> 4bbe3b885e8cd1907ab4cf9a41e862e74e24b5422297a4f2fe524e6a30ada2b4
> LICENSE
> diff --git a/package/containerd/containerd.mk b/package/containerd/containerd.mk
> index 83489a3abf..c4a6d854c3 100644
> --- a/package/containerd/containerd.mk
> +++ b/package/containerd/containerd.mk
> @@ -4,7 +4,7 @@
> #
>
> ################################################################################
>
> -CONTAINERD_VERSION = 1.6.21
> +CONTAINERD_VERSION = 1.6.22
> CONTAINERD_SITE = $(call github,containerd,containerd,v$(CONTAINERD_VERSION))
> CONTAINERD_LICENSE = Apache-2.0
> CONTAINERD_LICENSE_FILES = LICENSE
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-07 23:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 23:22 [Buildroot] [PATCH v1 1/1] package/containerd: bump version to v1.6.22 Christian Stewart via buildroot
2023-07-28 19:17 ` Thomas Petazzoni via buildroot
2023-08-30 11:04 ` Peter Korsgaard
2023-09-07 23:23 ` Stefan Agner [this message]
2023-09-07 23:28 ` Christian Stewart via buildroot
2023-09-07 23:50 ` Stefan Agner
2023-09-08 2:03 ` Christian Stewart via buildroot
2023-09-08 6:20 ` Stefan Agner
2023-09-15 21:48 ` Christian Stewart via buildroot
2023-09-25 10:08 ` Stefan Agner
2023-09-30 8:03 ` Peter Korsgaard
2023-10-02 18:28 ` Christian Stewart via buildroot
2023-10-04 9:59 ` Stefan Agner
2023-10-04 10:04 ` Christian Stewart via buildroot
2023-10-04 10:08 ` Stefan Agner
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=b73fb293249bcf48f42ebaed0f78f1c1@agner.ch \
--to=stefan@agner.ch \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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