Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to have support for udev in k3os #151

Closed
chtardif opened this issue Jul 24, 2019 · 6 comments
Closed

Need to have support for udev in k3os #151

chtardif opened this issue Jul 24, 2019 · 6 comments

Comments

@chtardif
Copy link

@chtardif chtardif commented Jul 24, 2019

Primary use case: OpenEBS/cStor not working without proper udev support in underlying OS

@jstebbins

This comment has been minimized.

Copy link

@jstebbins jstebbins commented Sep 19, 2019

FYI, Rook/EdgeFS also needs this to identify devices in a way that is persistent across reboots.

@Alxandr

This comment has been minimized.

Copy link
Contributor

@Alxandr Alxandr commented Jan 4, 2020

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)?

@liyimeng

This comment has been minimized.

Copy link
Contributor

@liyimeng liyimeng commented Jan 23, 2020

This is very easy to add, just install it in the base images.
I don’t suggest to have it by default since it increases the initrd size. If you need it, just add it and build from source. Easy job .

@dweomer dweomer added this to the v0.9.0 milestone Jan 28, 2020
@zube zube bot removed the [zube]: Backlog label Jan 28, 2020
dweomer added a commit to dweomer/k3os that referenced this issue Jan 28, 2020
@dweomer dweomer mentioned this issue Jan 28, 2020
dweomer added a commit to dweomer/k3os that referenced this issue Jan 28, 2020
dweomer added a commit to dweomer/k3os that referenced this issue Jan 28, 2020
@dweomer

This comment has been minimized.

Copy link
Member

@dweomer dweomer commented Jan 31, 2020

@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!

@jstebbins

This comment has been minimized.

Copy link

@jstebbins jstebbins commented Jan 31, 2020

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

+RUN rc-update add udev sysinit
+RUN rc-update add udev-trigger sysinit
+RUN rc-update add udev-settle sysinit

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.

@dweomer

This comment has been minimized.

Copy link
Member

@dweomer dweomer commented Jan 31, 2020

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

6 participants
You can’t perform that action at this time.