mirrors/talos-extensions
1
0
Fork 0
mirror of https://github.com/siderolabs/extensions.git synced 2025-08-05 22:07:14 +02:00
Code Issues Packages Projects Releases Wiki Activity
main
talos-extensions/drivers/gasket
History
Dmitry Sharshakov 5cd226e3ea
chore: build with new toolchain 
Move modules, firmware and libraries to accommodate usrmerged rootfs

Only use network where needed via new bldr, pre-download Go dependencies in prepare step, improve Go cache

Bump xen-guest-agent to make it build with current Alpine Rust

Signed-off-by: Dmitry Sharshakov <dmitry.sharshakov@siderolabs.com>
2025-02-10 16:00:19 +01:00
..
manifest.yaml fix: extension name in manifests 2024-05-08 19:26:30 +04:00
pkg.yaml chore: build with new toolchain 2025-02-10 16:00:19 +01:00
README.md docs: update documentation on installing extensions 2023-09-29 22:49:23 +04:00
vars.yaml feat: update dependencies 2024-05-09 21:28:23 +04:00

README.md

gasket-driver extension

Installation

See Installing Extensions.

Usage

By default, the device will be owned by UID and GID 0 and is only accessible by root. If you need to change this, you may do this by adding udev rules to your machine configuration like this, which would change the GID to 44 and give that group read/write permissions.

machine:
  udev:
    rules:
      - SUBSYSTEM=="apex", MODE="0660", GROUP="44"

Verifiying

You can verify the modules are enabled by reading the /proc/modules where it should show the module is live.

For example:

❯ talosctl -n 192.168.32.5  read /proc/modules
apex 20480 - - Live 0xffffffffc01c9000 (O)
gasket 94208 - - Live 0xffffffffc01aa000 (O)

In addition, if you actually have Coral module installed, you should be able to verify it's presence at /dev/apex_0.

For example:

❯ talosctl -n 192.168.32.5  ls -l /dev/apex_0
NODE           MODE          UID   GID   SIZE(B)   LASTMOD           NAME
192.168.32.5   Dcrw-rw----   0     44    0         Sep 10 18:15:52   apex_0