-
Notifications
You must be signed in to change notification settings - Fork 403
Need to have support for udev in k3os #151
Comments
FYI, Rook/EdgeFS also needs this to identify devices in a way that is persistent across reboots. |
Is this hard to add? Or is it just copying another package from upstream alpine (which as far as I've understood k3os is based on)? |
This is very easy to add, just install it in the base images. |
Addresses rancher#113 and rancher#151
Addresses rancher#113 and rancher#151
Addresses rancher#113 and rancher#151
@jstebbins and/or @chtardif If you have a test setup or some guidance (that hopefully doesn't require hours of reading) on how I can assert that your udev use-case is satisfied, I would very much welcome the input. Have any links to share? Also, please try the latest v.0.9.x release candidate! |
Unfortunately, my use case is rather difficult to set up. I had previously added udev myself, but I enabled the service by adding this to Dockerfile at the end
It looks like you enabled the udev service in a different way, but looks like you're missing udev-trigger and udev-settle? TBH, it's been so long I can't remember exactly why I added those last 2. Might just have copied an example I saw elsewhere. |
@jstebbins for some reason i had it in my head that they were triggered so long as udev was present but that doesn't seem to be the case. i will cut another RC with this change. |
Primary use case: OpenEBS/cStor not working without proper udev support in underlying OS
The text was updated successfully, but these errors were encountered: