From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: 64910@debbugs.gnu.org
Cc: Hilton Chain <hako@ultrarare.space>
Subject: [bug#64910] [PATCH 0/3] gnu: docker: Update to 20.10.25.
Date: Fri, 11 Aug 2023 16:01:27 +0800 [thread overview]
Message-ID: <87o7jej9d4.wl-hako@ultrarare.space> (raw)
In-Reply-To: <cover.1690513710.git.hako@ultrarare.space>
tags 64910 moreinfo
thanks
> Hilton Chain (3):
> gnu: runc: Update to 1.1.8.
> gnu: containerd: Update to 1.6.22.
> gnu: docker: Update to 20.10.25.
>
> gnu/packages/docker.scm | 18 +++++++++---------
> gnu/packages/virtualization.scm | 4 ++--
> 2 files changed, 11 insertions(+), 11 deletions(-)
>
>
> base-commit: 35c8d631d2bd63c64e863b5509f29fdcb7f856e6
> --
> 2.41.0
There's an issue that containerd fails to start, I'll address it.
next prev parent reply other threads:[~2023-08-11 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 3:11 [bug#64910] [PATCH 0/3] gnu: docker: Update to 20.10.25 Hilton Chain via Guix-patches via
2023-07-28 3:13 ` [bug#64910] [PATCH 1/3] gnu: runc: Update to 1.1.8 Hilton Chain via Guix-patches via
2023-07-28 3:13 ` [bug#64910] [PATCH 2/3] gnu: containerd: Update to 1.6.22 Hilton Chain via Guix-patches via
2023-07-28 3:13 ` [bug#64910] [PATCH 3/3] gnu: docker: Update to 20.10.25 Hilton Chain via Guix-patches via
2023-08-11 8:01 ` Hilton Chain via Guix-patches via [this message]
2023-08-11 10:45 ` [bug#64910] [PATCH v2 0/3] " Hilton Chain via Guix-patches via
2023-08-11 10:46 ` [bug#64910] [PATCH v2 1/3] gnu: runc: Update to 1.1.9 Hilton Chain via Guix-patches via
2023-08-11 10:46 ` [bug#64910] [PATCH v2 2/3] gnu: containerd: Update to 1.6.22 Hilton Chain via Guix-patches via
2023-08-11 10:46 ` [bug#64910] [PATCH v2 3/3] gnu: docker: Update to 20.10.25 Hilton Chain via Guix-patches via
2023-08-27 17:57 ` [bug#64910] [PATCH v2 0/3] " Christopher Baines
2023-08-29 15:16 ` bug#64910: " Hilton Chain via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7jej9d4.wl-hako@ultrarare.space \
--to=guix-patches@gnu.org \
--cc=64910@debbugs.gnu.org \
--cc=hako@ultrarare.space \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).