The repository 'http://cmc-cd-mirror.rnd.huawei.com/ubuntu jammy InRelease' is not signed.

遇到"The repository 'http://cmc-cd-mirror.rnd.huawei.com/ubuntu jammy InRelease' is not signed."错误通常表示你在尝试从一个未签名的Ubuntu软件存储库下载更新。这可能是由于几个原因：

1. **证书问题**：该镜像可能使用自签名证书，或者证书已过期或不受信任。要解决这个问题，你可以尝试添加存储库到信任的证书列表（仅限于你知道其来源可靠的情况下）。

   sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys <repository_key>

其中 `<repository_key>` 是你需要添加的密钥。如果知道具体的密钥ID，替换掉 `<repository_key>`。

2. **更新存储库列表**：确保你的apt缓存是最新的，可以运行以下命令：

   sudo apt update

3. **更换可信源**：如果华为的官方镜像不可信，你可以选择其他官方的Ubuntu镜像源，如`archive.ubuntu.com` 或 `security.ubuntu.com`。

4. **检查网络连接**：确保你能正常访问互联网，因为有时网络问题也可能导致此错误。

如果上述方法都不能解决问题，建议联系华为技术支持以确认该镜像是否正常或寻求其他解决方案。

相关问题

W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed. W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed. W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed. W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed. E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true' E: Sub-process returned an error code

这个错误是由于apt-key无法读取/etc/apt/trusted.gpg.d/目录下的文件，导致无法验证Ubuntu软件源的签名。解决这个问题的方法是：

1. 使用以下命令导入缺失的公钥：

   sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 871920D1991BC93C

注意替换上述命令中的871920D1991BC93C为您的错误中所提到的缺失的公钥。

2. 如果上述命令无效，可以尝试使用以下命令：

   sudo apt-key adv --refresh-keys --keyserver keyserver.ubuntu.com

3. 如果上述命令仍然无效，可以尝试手动下载公钥并导入。首先，找到缺失的公钥的ID，例如871920D1991BC93C。然后，使用以下命令下载公钥：

   sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 871920D1991BC93C

最后，使用以下命令将公钥导入系统：

   sudo apt-key add /path/to/downloaded/key

注意替换上述命令中的/path/to/downloaded/key为您下载的公钥文件的路径。

完成上述步骤后，再次运行apt-get update应该就不会出现上述错误了。

Hit:1 http://mirrors.aliyun.com/docker-ce/linux/ubuntu jammy InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:3 https://download.docker.com/linux/ubuntu jammy InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Get:5 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Get:6 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Reading package lists... Done W: http://mirrors.aliyun.com/docker-ce/linux/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. W: https://download.docker.com/linux/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. E: Release file for http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease is not valid yet (invalid for another 1h 8min 26s). Updates for this repository will not be applied. E: Release file for http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease is not valid yet (invalid for another 1h 8min 14s). Updates for this repository will not be applied.

这个错误看起来是您的Ubuntu系统更新源的问题。其中的一些源似乎已经过期或尚未更新。

您可以尝试等待一段时间，然后再次尝试运行更新命令。通常情况下，这些更新源会在一段时间后自动更新并恢复正常。

如果问题仍然存在，请尝试使用其他的Ubuntu更新源，例如清华大学的更新源（http://mirrors.tuna.tsinghua.edu.cn/ubuntu/）或中科大的更新源（http://mirrors.ustc.edu.cn/ubuntu/）。

您可以按照以下步骤更改更新源：

1. 打开终端并输入以下命令以备份当前的更新源列表：

   sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak

2. 使用您选择的更新源替换原始更新源。例如，如果您要使用清华大学的更新源，请使用以下命令替换更新源：

   sudo sed -i 's/archive.ubuntu.com/mirrors.tuna.tsinghua.edu.cn/g' /etc/apt/sources.list

3. 运行以下命令以更新软件包列表：

   sudo apt-get update

如果更新成功，则应该没有错误消息。

4. 最后，您可以尝试重新运行您的Docker安装命令以重新安装Docker。

如果问题仍然存在，请提供更多信息，以便我更好地帮助您解决问题。