This message was deleted.

Hi Andy, do you have any target external storage and the CSI driver for the question?

Portworx CSI supports it with a Flasharray. But it requires the host OS to be able to mount nvme luns. so the real question is does sle-micro for harvester come with the nvme binaries/packages?

I got master build: should be closed to 1.8

$ rpm -qa | grep nvme
libnvme-mi1-1.11+17.g6d55624d-160000.1.1.x86_64
libnvme1-1.11+17.g6d55624d-160000.1.1.x86_64
nvme-cli-2.11+29.g35e62868-160000.1.1.x86_64

ok cool so the answer should be yes.. nice!

yeah I've used like this before:

docker run -it registry.opensuse.org/isv/rancher/harvester/os/dev/main/baseos:latest rpm -qa | grep nvme
libnvme-mi1-1.11+17.g6d55624d-160000.1.1.x86_64
libnvme1-1.11+17.g6d55624d-160000.1.1.x86_64
nvme-cli-2.11+29.g35e62868-160000.1.1.x86_64

edit: speaking of it'd be nice if historical images/tags could be left in this repo? happened to be trying to do kmod build and realized

:latest

is out of sync w/ v1.8.0 and old images look gone?

6.12.0-160000.28

vs

6.12.0-160000.32

oh nice

@prehistoric-morning-49258 I'm not sure whether we can change

<http://registry.opensuse.org/isv/rancher/harvester/os/dev/main/baseos:latest|registry.opensuse.org/isv/rancher/harvester/os/dev/main/baseos:latest>

to keep historical images (there's a big long story there with how the build service works and interacts with the registry), but... I've got https://github.com/harvester/harvester/issues/10418 on my plate, which is about standardizing adding extra kernel modules, and as part of that I was thinking of maybe making a more generic version of this thing: https://hub.docker.com/r/rancher/harvester-nvidia-driver-toolkit/tags which would only include the kernel headers (and not the nvidia build stuff), and could potentially be used to help build arbitrary modules. That would be tagged with every harvester release, and thus (potentially) be something you could rely on.

that would be amazing. btw Claude churned for a good while on this problem, and finally tracked down that it was possible to use bci images to match the kernel:

# Default targets kernel 6.12.0-160000.28-default (Harvester 1.8.0).

ARG BASE_IMAGE=<http://registry.suse.com/bci/bci-sle16-kernel-module-devel:16.0-28.12|registry.suse.com/bci/bci-sle16-kernel-module-devel:16.0-28.12>

there was actually an AI eureka moment in the log when that was discovered, it was pretty great. appears to work

oooh, excellent, thanks for the tip!