仓库似乎没有更新手动更新相关依赖后无法正常构建

**【缺陷描述】：Dockerfile及yum repo没有更新 手动更换为最新版本无法构建成品镜像**

**【缺陷所属的os版本】NestOS 22.04-lts-sp4/24.03-lts**

**【内核版本】6.6.0-35.1.1**

**【缺陷所属软件及版本号】nestos-assembler**

**【环境信息】**
硬件信息

- x86_64平台Linux docker

软件信息

- qemu-8.2.0-17.oe2403
- kernel-6.6.0-35.1.1.oe2403.x86_64
- docker-28.3.0

网络信息

- 无特殊组网

**【问题复现步骤】：**
1. 将Dockerfile的基础镜像升级到24.03-lts
```Dockerfile
...
FROM openeuler-24.03-lts
...
```
2. 将build.sh自动填入的repo信息升级到24.03-lts
```bash
...
    echo -e "[${version_id}-NestOS]\nname=NestOS\nenabled=1\nmetadata_expire=1m\nbaseurl=https://repo.openeuler.org/openEuler-24.03-LTS/EPOL/multi_version/NestOS/For-Container/20240903/$arch/\ngpgcheck=0\npriority=2\nskip_if_unavailable=False\n" >> /etc/yum.repos.d/nestos-sp4.repo
    echo -e "[${version_id}-everything]\nname=everything\nenabled=1\nmetadata_expire=1m\nbaseurl=https://repo.openeuler.org/openEuler-24.03-LTS/everything/$arch/\ngpgcheck=0\nskip_if_unavailable=False\n" >> /etc/yum.repos.d/nestos-sp4.repo
    echo -e "[${version_id}-EPOL]\nname=EPOL\nenabled=1\nmetadata_expire=1m\nbaseurl=https://repo.openeuler.org/openEuler-24.03-LTS/EPOL/main/$arch/\ngpgcheck=0\nskip_if_unavailable=False\n" >> /etc/yum.repos.d/nestos-sp4.repo
    echo -e "[${version_id}-extra]\nname=extra\nenabled=1\nmetadata_expire=1m\nbaseurl=https://nestos.org.cn/NestOS-24.03-LTS/For-Container/20240903/$arch/\ngpgcheck=0\npriority=1\nskip_if_unavailable=False\n" >> /etc/yum.repos.d/nestos-sp4.repo
...
```
3. 使用docker build构建镜像
4. 使用首页给出的nosa脚本
```bash
#!/bin/bash

sudo docker run --rm  -it --security-opt label=disable --privileged --user=root                        \
           -v ${PWD}:/srv/ --device /dev/kvm --device /dev/fuse --network=host                                 \
           --tmpfs /tmp -v /var/tmp:/var/tmp -v /root/.ssh/:/root/.ssh/   -v /etc/pki/ca-trust/:/etc/pki/ca-trust/                                        \
           ${COREOS_ASSEMBLER_CONFIG_GIT:+-v $COREOS_ASSEMBLER_CONFIG_GIT:/srv/src/config/:ro}   \
           ${COREOS_ASSEMBLER_GIT:+-v $COREOS_ASSEMBLER_GIT/src/:/usr/lib/coreos-assembler/:ro}  \
           ${COREOS_ASSEMBLER_CONTAINER_RUNTIME_ARGS}                                            \
           ${COREOS_ASSEMBLER_CONTAINER:-nestos-assembler:your_tag} "$@"
```
5. 创建环境文件夹并构建
```
mkdir nestos-test-1
cd nestos-test-1
nosa init --branch NestOS-24.03-LTS https://gitee.com/openeuler/nestos-config.git NestOS-For-Container
nosa fetch && nosa build
```
**【实际结果】**
OCI镜像是正常构建的。
在构建qemu镜像的过程中卡住不动了。
**【期望结果】**
类似于上游项目Fedora CoreOS，应无需手动修改即能正确输出OCI镜像和qemu硬盘镜像。
如图![](https://foruda.gitee.com/images/1752483876737328965/4c4debc9_14904125.png "屏幕截图")
**【其他相关附件信息】**
NestOS For Virt似乎是基于oemaker的，nosa init会报错。
![](https://foruda.gitee.com/images/1752485167987470768/7a37d2e4_14904125.png "屏幕截图")
卡住的时候，应该是正在用supermin构建的kernel initrd和rootfs中启动qemu虚拟机。并在虚拟机中启动构建，放入新的qcow2镜像中。
```bash
+ kola qemuexec -m 2048 --auto-cpus -U --workdir none --console-to-file /srv/tmp/build.qemu/runvm-console.txt --bind-rw /srv,workdir -- -drive if=none,id=root,format=raw,snapshot=on,file=/srv/tmp/build.qemu/supermin.build/root,index=1 -device virtio-blk,drive=root -kernel /srv/tmp/build.qemu/supermin.build/kernel -initrd /srv/tmp/build.qemu/supermin.build/initrd -no-reboot -nodefaults -device virtio-serial -append 'root=UUID=911a9f24-3672-4004-8172-4adbfd85ebff console=ttyS0,115200n8 selinux=1 enforcing=0 autorelabel=1' -device virtserialport,chardev=virtioserial0,name=cosa-cmdout -chardev stdio,id=virtioserial0 -drive if=none,id=target,format=qcow2,file=/srv/tmp/build.qemu/nestos-24.03-LTS.20250714.0-qemu.x86_64.qcow2.tmp,cache=unsafe -device virtio-blk,serial=target,drive=target
configure accelerator pc-i440fx-8.2 start
machine init start
device init start
add qdev virtio-rng-pci:none success
add qdev virtio-rng-pci:none success
add qdev tpm-tis:none success
add qdev tpm-tis:none success
add qdev virtio-blk-pci:none success
add qdev virtio-blk:none success
add qdev virtio-serial-pci:none success
add qdev virtio-serial:none success
add qdev virtserialport:none success
virtio serial port 1 send control message event = 6, value = 1
virtio serial port 1 send control message event = 1, value = 1
add qdev virtserialport:none success
add qdev virtio-blk-pci:none success
add qdev virtio-blk:none success
add qdev virtio-net-pci:none success
add rom file: virtio-net-pci.rom
add qdev virtio-net-pci:none success
add qdev virtio-serial-pci:none success
add qdev virtio-serial:none success
add qdev virtserialport:none success
virtio serial port 1 send control message event = 6, value = 1
virtio serial port 1 send control message event = 1, value = 1
add qdev virtserialport:none success
add qdev vhost-user-fs-pci:none success
add qdev vhost-user-fs-pci:none success
reset all devices
qmp cont is received and vm is started
{"timestamp": {"seconds": 1752479760, "microseconds": 927873}, "event": "RESUME"}
qemu enter main_loop
virtio-blk device status is 3 that means DRIVER
virtio-blk device status is 11 that means DRIVER
virtio-blk device status is 15 that means DRIVER OK
virtio-blk device status is 3 that means DRIVER
virtio-blk device status is 11 that means DRIVER
virtio-blk device status is 15 that means DRIVER OK
qmp_cmd_name: qmp_capabilities, arguments: {}
qmp_cmd_name: qmp_capabilities, arguments: {}
virtio-rng device status is 1 that means ACKNOWLEDGE
virtio-blk device status is 1 that means ACKNOWLEDGE
virtio-serial device status is 1 that means ACKNOWLEDGE
virtio-blk device status is 1 that means ACKNOWLEDGE
virtio-net device status is 1 that means ACKNOWLEDGE
virtio-serial device status is 1 that means ACKNOWLEDGE
virtio-user-fs device status is 1 that means ACKNOWLEDGE
virtio-rng device status is 3 that means DRIVER
virtio-rng device status is 11 that means DRIVER
virtio-rng device status is 15 that means DRIVER OK
virtio-blk device status is 3 that means DRIVER
virtio-blk device status is 11 that means DRIVER
virtio-blk device status is 15 that means DRIVER OK
virtio-blk device status is 3 that means DRIVER
virtio-blk device status is 11 that means DRIVER
virtio-blk device status is 15 that means DRIVER OK
virtio-serial device status is 3 that means DRIVER
virtio-serial device status is 11 that means DRIVER
virtio-serial device status is 15 that means DRIVER OK
virtio serial port '4294967295' handle control message event = 0, value = 1
virtio serial port 1 send control message event = 1, value = 1
virtio-serial device status is 3 that means DRIVER
virtio-serial device status is 11 that means DRIVER
virtio serial port '1' handle control message event = 3, value = 1
virtio serial port 1 send control message event = 6, value = 1
virtio-serial device status is 15 that means DRIVER OK
virtio serial port '4294967295' handle control message event = 0, value = 1
virtio serial port 1 send control message event = 1, value = 1
virtio serial port '1' handle control message event = 3, value = 1
virtio serial port 1 send control message event = 6, value = 1
virtio-net device status is 3 that means DRIVER
virtio-net device status is 11 that means DRIVER
virtio-net device status is 15 that means DRIVER OK
virtio-user-fs device status is 3 that means DRIVER
virtio-user-fs device status is 11 that means DRIVER
virtio-user-fs device status is 15 that means DRIVER OK
{"timestamp": {"seconds": 1752479763, "microseconds": 239902}, "event": "NIC_RX_FILTER_CHANGED", "data": {"path": "/machine/peripheral-anon/device[6]/virtio-backend"}}
virtio serial port '1' handle control message event = 6, value = 1
virtio serial port 1 send control message event = 6, value = 0
```
在runvm-console.txt，也就是命令行输出中，发现了这样的log：
```bash
+ bash /srv/tmp/build.qemu/cmd.sh
+ tee /dev/virtio-ports/cosa-cmdout
+ BOOTPN=3
+ ROOTPN=4
+ [[ 0 -eq 1 ]]
[    5.921909][  T313]  vdb: vdb1 vdb2 vdb3 vdb4
[    6.941680][  T426]  vdb: vdb1 vdb2 vdb3 vdb4
[    7.482987][  T444] SGI XFS with ACLs, security attributes, quota, no debug enabled
[    7.486979][  T443] XFS (vdb4): Mounting V5 Filesystem 910678ff-f77e-4a7d-8d53-86f2ac47a823
[    7.494173][  T443] XFS (vdb4): Ending clean mount
[    7.512205][  T460] EXT4-fs (vdb3): mounted filesystem 96d15588-3596-4b3c-adca-a2ff7279ea63 r/w with ordered data mode. Quota mode: none.
[   31.779909][ T1679] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[   31.783022][ T1679] device-mapper: uevent: version 1.0.3
[   31.784351][ T1679] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
[   32.166627][ T1678] VFS: Open an exclusive opened block device for write [vdb]. current [1678 grub2-install]. parent [386 create_disk.sh]
[   32.169126][ T1678] VFS: Open an exclusive opened block device for write [vdb]. current [1678 grub2-install]. parent [386 create_disk.sh]
[   32.307849][ T1694] EXT4-fs (vdb3): re-mounted 96d15588-3596-4b3c-adca-a2ff7279ea63 ro. Quota mode: none.
[   32.413278][ T1700] EXT4-fs (vdb3): unmounting filesystem 96d15588-3596-4b3c-adca-a2ff7279ea63.
[   32.548687][ T1700] XFS (vdb4): Unmounting Filesystem 910678ff-f77e-4a7d-8d53-86f2ac47a823
```
似乎并没有构建完成，虚拟硬盘就被umount掉了，很奇怪。

**【缺陷详情及分析指导参考链接】**

openEuler/nestos-assembler

内容风险标识

评论 (2)

openEuler/nestos-assembler .gitee-modal { width: 500px !important; }

内容风险标识