[Imager] Segmentation Violation when creating new images #8987
Assignees
Comments
|
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: .xzThough that leads to a discussion that talos/pkg/imager/profile/profile.go Line 103 in fbde9c5 |
|
yep, it's actually a bug that it crashes, as |
|
Is there also some limitation on the tag/version format ? This make it crash: then I changed the |
|
@camrossi if you could attach a full stack trace, we are happy to fix this |
|
Hi @smira ! Sure thing! This is the output from my GitHub Action pipeline |
smira
added a commit
to smira/talos
that referenced
this issue
Jan 13, 2025
Fixes siderolabs#8987 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
smira
added a commit
to smira/talos
that referenced
this issue
Jan 16, 2025
Fixes siderolabs#8987 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com> (cherry picked from commit 8de1975)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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-rk3398build 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.yamlLogs
Environment
The text was updated successfully, but these errors were encountered: