When running a bink cluster with a composefs-backed bootc image, cloud-init-main.service exits with status 1 due to two commands in the user-data template that assume a traditional ostree layout:
- sed -i '/swap/d' /etc/fstab — /etc/fstab does not exist on composefs images.
- The TargetImgRef block constructs an ostree origin file path using
bootc status --json | jq -r '.status.booted.ostree.checksum', which returns null on composefs (no traditional ostree deployment). This results in sed trying to read /ostree/deploy/default/deploy/null..origin, which doesn't exist. The failure in this block causes cc_scripts_user to fail, which makes cloud-init exit non-zero
When running a bink cluster with a composefs-backed bootc image, cloud-init-main.service exits with status 1 due to two commands in the user-data template that assume a traditional ostree layout:
bootc status --json | jq -r '.status.booted.ostree.checksum', which returns null on composefs (no traditional ostree deployment). This results in sed trying to read /ostree/deploy/default/deploy/null..origin, which doesn't exist. The failure in this block causes cc_scripts_user to fail, which makes cloud-init exit non-zero