红帽全球峰会10.18. 容器
Podman 和 bootc 没有共享同样的注册中心登录过程
在拉取镜像时，Podman 和 bootc 使用不同的注册中心登录过程。因此，如果您使用 Podman 登录到镜像，登录到 bootc 的注册中心将不适用于该镜像。当您为 RHEL 系统安装镜像模式时，使用以下命令登录到 registry.redhat.io：
podman login registry.redhat.io <username_password>
# podman login registry.redhat.io <username_password>
然后，您可以使用以下命令尝试切换到 registry.redhat.io/rhel9/rhel-bootc 镜像：
bootc switch registry.redhat.io/rhel9/rhel-bootc:9.4
# bootc switch registry.redhat.io/rhel9/rhel-bootc:9.4您应该可以看到以下消息：
Queued for next boot: registry.redhat.io/rhel9/rhel-bootc:9.4
Queued for next boot: registry.redhat.io/rhel9/rhel-bootc:9.4但是显示了一个错误：
ERROR Switching: Pulling: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
ERROR Switching: Pulling: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
临时解决方案：按照步骤 配置容器拉取 secret，以使用带有 bootc 的经过验证的注册中心。
Jira:RHELDOCS-18471[1]
启用 composefs 后，cloud-init growpart 跳过
启用 composefs 时，如果您从通用基础镜像生成一个镜像，则 rootfs 将不会增大文件系统，提示一个类似如下的错误：
2024-04-30 17:27:53,543 - cc_growpart.py[DEBUG]: '/' SKIPPED: stat of 'overlay' failed: [Errno 2] No such file or directory: 'overlay'
2024-04-30 17:27:53,543 - cc_growpart.py[DEBUG]: '/' SKIPPED: stat of 'overlay' failed: [Errno 2] No such file or directory: 'overlay'
临时解决方案：您可以通过在容器中指定 rootfs 默认大小，而不是在实例创建时动态选择 100G 来添加自定义的 growpart，以便能够在容器中写一个分区配置。
FIPS bootc 镜像创建在启用了 FIPS 的主机上失败
由于 update-crypto-policies 软件包，使用启用了 FIPS 模式的 Podman 构建磁盘镜像失败，退出码为 3 ：
Enable the FIPS crypto policy crypto-policies-scripts is not installed by default in RHEL-10
# Enable the FIPS crypto policy
# crypto-policies-scripts is not installed by default in RHEL-10
RUN dnf install -y crypto-policies-scripts && update-crypto-policies --no-reload --set FIPS临时解决方案：构建具有禁用了 FIPS 模式的 bootc 镜像。
磁盘空间不足可能导致部署失败
在没有足够可用磁盘空间的软件包模式系统上部署 bootc 容器镜像可能会导致安装错误，并阻止系统引导。确保有足够的磁盘空间供镜像安装，并在部署前调整配置的逻辑卷。
Jira:RHELDOCS-19948[1]
Azure 上标记为 LVM 的 RHEL 镜像需要调整默认布局
当在 Azure 上使用 system-reinstall-bootc 或 bootc install 时，标记为 LVM 的 RHEL 镜像需要调整默认布局。
临时解决方案：使用标记为 RAW 的 RHEL 镜像。这不需要调整默认布局。
Jira:RHELDOCS-19945[1]
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}