mirrors/talos-extensions
1
0
Fork 0
mirror of https://github.com/siderolabs/extensions.git synced 2025-09-28 17:11:21 +02:00
Code Issues Packages Projects Releases Wiki Activity
talos-extensions/drivers/gasket
History
Andrey Smirnov 0ba9f81043
docs: update documentation on installing extensions 
Remove deprecated `.machine.install.extensions`, point to Talos
documentation.

Once Image Factory is live, we can point to it.

Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
2023-09-29 22:49:23 +04:00
..
manifest.yaml
feat: add gasket driver
2022-09-22 13:29:02 +05:30
pkg.yaml
chore: use standard PKGS variable
2023-02-22 15:29:58 +05:30
README.md
docs: update documentation on installing extensions
2023-09-29 22:49:23 +04:00
vars.yaml
feat: update releases
2023-09-27 21:15:47 +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