unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
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 v2 0/3] gnu: docker: Update to 20.10.25.
Date: Fri, 11 Aug 2023 18:45:05 +0800	[thread overview]
Message-ID: <cover.1691750473.git.hako@ultrarare.space> (raw)
In-Reply-To: <cover.1690513710.git.hako@ultrarare.space>

V1 -> V2:
  - runc@1.1.9
  - Fix containerd starting issue.

`make check-system TESTS=docker' passes.


Details on the issue:

Error message:
--8<---------------cut here---------------start------------->8---
msg="failed to load plugin io.containerd.grpc.v1.cri"
error="invalid plugin config: no corresponding runtime configured in `containerd.runtimes` for `containerd` `default_runtime_name` = \"/gnu/store/...-runc-1.1.9/sbin/runc\""
--8<---------------cut here---------------end--------------->8---

The message comes from pkg/cri/config/config.go:
--8<---------------cut here---------------start------------->8---
if _, ok := c.ContainerdConfig.Runtimes[c.ContainerdConfig.DefaultRuntimeName]; !ok {
	return fmt.Errorf("no corresponding runtime configured in `containerd.runtimes` for `containerd` `default_runtime_name = \"%s\"", c.ContainerdConfig.DefaultRuntimeName)
}
--8<---------------cut here---------------end--------------->8---

It expects there's `ContainerdConfig.DefaultRuntimeName' within
`ContainerdConfig.Runtimes'.

And from the relevant code in pkg/cri/config/config_unix.go and the
package definion, "runc" the `DefaultRuntimeName' was substituted to a
store path, but not "runc" in `Runtimes'.

So [...].Runtimes["/gnu/store/...-runc-1.1.9/sbin/runc"] fails.
--8<---------------cut here---------------start------------->8---
func DefaultConfig() PluginConfig {
	[...]
	return PluginConfig{
		[...]
		ContainerdConfig: ContainerdConfig{
			[...]
			DefaultRuntimeName: "runc",
			Runtimes: map[string]Runtime{
				"runc": {
					[...]
				},
			},
			[...]
		},
		[...]
	}
}
--8<---------------cut here---------------end--------------->8---

There's no functional change in those two files between 1.6.6 and
1.6.22, I wonder why this wasn't an issue before...

Thanks

Hilton Chain (3):
  gnu: runc: Update to 1.1.9.
  gnu: containerd: Update to 1.6.22.
  gnu: docker: Update to 20.10.25.

 gnu/packages/docker.scm         | 25 +++++++++++++++----------
 gnu/packages/virtualization.scm |  4 ++--
 2 files changed, 17 insertions(+), 12 deletions(-)


base-commit: ad4520b92662e42d7d0b1e648b2068300dbb95c8
--
2.41.0




  parent reply	other threads:[~2023-08-11 10:47 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 ` [bug#64910] [PATCH 0/3] " Hilton Chain via Guix-patches via
2023-08-11 10:45 ` Hilton Chain via Guix-patches via [this message]
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=cover.1691750473.git.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).