No public key during crio install on Debian 12

[is-it-ayush]

Hi, I'm trying to install cri-o so I could proceed with the installation of kubeadm on a local debian 12 virtual machine. I followed the install instructions as defined here for "apt" and set $VERSION=1.29.1 and $OS=Debian_12. When I ran apt-update (as root). I got the following,

root@node:/home/one# apt update
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://deb.debian.org/debian buster-backports InRelease
Get:5 http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.23/Debian_10  InRelease [1610 B]
Err:5 http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.23/Debian_10  InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4D64390375060AA4
Ign:6 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o://  InRelease
Ign:7 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.29.1/Debian_12  InRelease
Get:8 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/Debian_12  InRelease [1634 B]
Err:8 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/Debian_12  InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4D64390375060AA4
Err:9 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o://  Release
  404  Not Found [IP: 195.135.223.226 443]
Err:10 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.29.1/Debian_12  Release
  404  Not Found [IP: 195.135.223.226 443]
Reading package lists... Done
W: GPG error: http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.23/Debian_10  InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4D64390375060AA4
E: The repository 'http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.23/Debian_10  InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/Debian_12  InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4D64390375060AA4
E: The repository 'https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/Debian_12  InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o://  Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.29.1/Debian_12  Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

I manually navigated to https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.29.1/Debian_12 and indeed there is no repository hosting Release.key which makes sense. How should I proceed with the install?

[kwilczynski]

Hi @is-it-ayush, thank you for getting in touch.

For releases 1.29 and newer, the package repository has moved.

Check the following blog post:

• CRI-O is moving towards pkgs.k8s.io

More details can be found at cri-o/packaging project.

[is-it-ayush]

Thank you @kwilczynski! I suspect the docs are broken then since they still refer to OBS (OpenSuse) setup which no longer hosts the latest keys and binaries for crio. Are there any plans for updating it?