-
Notifications
You must be signed in to change notification settings - Fork 34
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
Unable to build custom kernel module in 2605.9.0 #298
Comments
The build_image script invokes the create_dev_container function, and passes the `FLAGS_group` as param. Use the param, to generate the binhost URL instead of using the DEFAULT_GROUP which stays as developer always. Fixes: flatcar/Flatcar#298 Signed-off-by: Sayan Chowdhury <[email protected]>
Hey there! Thanks for the report! The fix for it has been merged and will be present in the next patch release for each channel. In the meantime, if you need to build the module, you can modify the |
The build_image script invokes the create_dev_container function, and passes the `FLAGS_group` as param. Use the param, to generate the binhost URL instead of using the DEFAULT_GROUP which stays as developer always. Fixes: flatcar/Flatcar#298 Signed-off-by: Sayan Chowdhury <[email protected]>
The build_image script invokes the create_dev_container function, and passes the `FLAGS_group` as param. Use the param, to generate the binhost URL instead of using the DEFAULT_GROUP which stays as developer always. Fixes: flatcar/Flatcar#298 Signed-off-by: Sayan Chowdhury <[email protected]>
The build_image script invokes the create_dev_container function, and passes the `FLAGS_group` as param. Use the param, to generate the binhost URL instead of using the DEFAULT_GROUP which stays as developer always. Fixes: flatcar/Flatcar#298 Signed-off-by: Sayan Chowdhury <[email protected]>
Unfortunately this fix re-opens a can of worms - the build fails on what seems a regressions of
Adding |
Huh, that's interesting, but I think it's unrelated to this bug (which was due to a bad URL in the dev container) and something perl specific. Could you please open a new issue about this? In that new issue, please include whether you're cross compiling or not (the old bug you pointed to was about cross compiling). |
Description
Build of a custom kernel module fails on 2605.9.0 - the same process is successful on 2605.8.0/
Impact
Production env is dependant on the module in question - blocked from upgrading.
Environment and steps to reproduce
ami-01005e70742a799fe
Expected behavior
build is successful
Additional information
Since we're building wireguard, the issue isn't relevant to beta and alpha build where it is part of the kernel.
Thank you for the great work on Flatcar and otherwise :)
The text was updated successfully, but these errors were encountered: