-
|
Hey, I'm trying to build my custom extensions for
I'm building them this way: # pkgs
make thunderbolt-pkg PLATFORM=amd64 USERNAME=ajgon PUSH=true
# extensions
make thunderbolt PLATFORM=amd64 USERNAME=ajgon PUSH=trueand eventually ending up with:
Then I'm installing extension to mine machine (only relevant part of the config): machine:
kernel:
modules:
- name: thunderbolt_net
install:
image: ghcr.io/siderolabs/installer:v1.5.0-alpha.2-4-g5e13cafe5
extensions:
- image: ghcr.io/ajgon/thunderbolt:v1.5.0-alpha.2-dirtySo far so good, the modules are extracted and installed properly. Hower when I'm loading them, I'm getting and I'm bit lost. I based my module on usb-modem-drivers pkg and (usb-modem-drivers extension](https://github.com/siderolabs/extensions/tree/main/drivers/usb-modem) - and usb-modem is working for me. Since thunderbolt is basically a copy-paste of that approach, I assume I'm doing something wrong on build/using Makefile phase.
Also this machine has secureboot disabled. At this point, I'm out of ideas, and any hint will be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
This is probably due to buildkit being aggressive with dropping caches, would recommend to create a builder with a custom config like here: https://github.com/siderolabs/build-container/blob/main/hack/scripts/setup-ci#L12 https://github.com/siderolabs/build-container/blob/main/hack/scripts/buildkit.toml |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunatelly it didn't help. I used the provided docker buildx create --name mybuild --buildkitd-flags "--allow-insecure-entitlement security.insecure" --driver-opt image="docker.io/moby/buildkit:v0.11.6" --platform linux/amd64 --driver docker-container --config ./buildkit.toml --useAnd double checked, that new image was built using this builder. I also dropped all caches before-head to start clean. Still no luck :( |
Beta Was this translation helpful? Give feedback.
-
|
Found the issue, let me answer for anyone stumbling into this: The problem was, that I was using default talos installer image with kernel built by talos team, and with random signing key used by it. So when I introduced my image with thunderbolt module, naturally I didn't have this key and another one was created - thus creating divergence. After I built my own kernel and my own installer using this guide everything clicked. P.S. I think the kernel building guide has a mistake, the following line didn't work for me: COPY --from=<custom kernel image> /lib/modules /lib/moduleshad to replace it to COPY --from=<custom kernel image> /lib/modules /kernel/lib/modulesto make everything work. |
Beta Was this translation helpful? Give feedback.
-
This is a small interim change for 1.5 (would have a better solution before release) The easy way to test is to edit the dockerfile of Talos repo, point to the custom kernel image and run |
Beta Was this translation helpful? Give feedback.
Found the issue, let me answer for anyone stumbling into this:
The problem was, that I was using default talos installer image with kernel built by talos team, and with random signing key used by it. So when I introduced my image with thunderbolt module, naturally I didn't have this key and another one was created - thus creating divergence.
After I built my own kernel and my own installer using this guide everything clicked.
P.S. I think the kernel building guide has a mistake, the following line didn't work for me:
COPY --from=<custom kernel image> /lib/modules /lib/moduleshad to replace it to
COPY --from=<custom kernel image> /lib/modules /kernel/lib/modulesto make everything work.