| kata-irc-bot | <anastassios.nanos> ok, so update on this: the diff between the non-working rootfs and the working one (on the exact norbjd's setup) is this: ```--- /mnt1/var/lib/osbuilder/osbuilder.yaml 2022-05-04 17:28:15.000000000 +0000 +++ /mnt2/var/lib/osbuilder/osbuilder.yaml 2022-06-14 08:05:09.000000000 +0000 @@ -2,26 +2,23 @@ osbuilder: url: "https://github.com/kata-containers/kata-containers/tools/osbuilder" version: "unknown" | 08:55 |
|---|---|---|
| kata-irc-bot | -rootfs-creation-time: "2022-05-04T17:28:15.233775972+0000Z" +rootfs-creation-time: "2022-06-14T08:05:09.908044759+0000Z" description: "osbuilder rootfs" file-format-version: "0.0.2" architecture: "x86_64" base-distro: name: "Clear" - version: "36260" + version: "36480" packages: default: - - "chrony" - "iptables-bin" - "kmod-bin" - "libseccomp" - "libudev0-shim" - - "systemd" - - | 08:55 |
| kata-irc-bot | "util-linux-bin" extra: agent: url: "https://github.com/kata-containers/kata-containers" name: "kata-agent" - version: "2.4.1" - agent-is-init-daemon: "no" + version: "2.5.0-alpha2" + agent-is-init-daemon: "yes"``` | 08:55 |
| kata-irc-bot | <anastassios.nanos> I suspect there's something going on with systemd but let's not jump to conclusions until I've tested that | 08:55 |
| kata-irc-bot | <anastassios.nanos> so, yeap, the `AGENT_INIT=yes` makes the difference -- if we choose to ommit this while building the rootfs image, fc won't boot correctly | 09:05 |
| kata-irc-bot | <fidencio> Oh that's interesting and deserves an issue reported. Is it only happening with Cloud Hypervisor? | 09:20 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!