Open preeefix opened 1 month ago
In this particular case, you're generating a disk image, but disk image options are not specified:
output:
kind: image
imageOptions:
diskSize: 8589934592
diskFormat: raw
outFormat: .xz
Sometimes, rereading the docs would lead to a better. And not filing GH Issues when I'm exhausted.
Ended up getting it to build correctly with the following profile.yaml.
arch: arm64
platform: metal
secureboot: false
version: v1.7.5
overlay:
name: libretech-roc-rk3328-cc
image:
imageRef: ghcr.io/preeefix/sbc-rockchip:0c603d0-dirty
output:
kind: image
imageOptions:
diskSize: 1306525696
diskFormat: raw
outFormat: .xz
Though that leads to a discussion that imager
doesn't fail in https://github.com/siderolabs/talos/blob/fbde9c556f0107734ff1216ea80d9156c35d4e3c/pkg/imager/profile/profile.go#L103 as part of the validation, though likely because the entire imageOptions block doesn't exist.
yep, it's actually a bug that it crashes, as imageOptions
is nil
in this case
Bug Report
In the proccess of bringing up a new board on Talos (LibreTech ROC-RK3328-CC), manually building the overlay causes a segmentation violation during imager builds.
Description
A friend of mine has some LibreTech ROC-RK3328-CC boards that he'd like to include into his existing Talos cluster and asked if I could build an image for them.
I started out by using the OrangePi as a base in the siderolabs/sbc-rockchip respository. I managed to get the image to build (available as ghcr.io/preeefix/sbc-rockchip) but when using the included
profile.yaml
, all I would receive were segmentation violations.I followed this up by creating a clean overlay via siderolabs/sbc-template, with only the
roc-cc-rk3398
build setup (just u-boot), and it again compiles and saves the container, but imager spits out a segmentation violation.It's likely that I'm missing something, but after searching around I'm unable to determine what's going wrong.
profile.yaml
Logs
Environment