Add fix for building libnl3 on Ubuntu 24.04 #22093
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When building libnl3 inside a container with a newer kernel (such as what is used on Ubuntu 24.04), some commands to create a private network namespace may fail due to restrictions. Backport a patch from libnl3 to handle such cases. Signed-off-by: Saikrishna Arcot <[email protected]>
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
qiluo-msft
approved these changes
Mar 20, 2025
saiarcot895
added a commit
to saiarcot895/sonic-buildimage
that referenced
this pull request
Apr 10, 2025
Why I did it When building libnl3 inside a container with a newer kernel (such as what is used on Ubuntu 24.04), some commands to create a private network namespace may fail due to restrictions. This was seen in libnl3's own Github Actions CI, and is now seen on build machines running Ubuntu 24.04 as the host with kernel 6.8. Work item tracking Microsoft ADO (number only): 31902668 How I did it Backport a patch from libnl3 to handle such cases.
yanjundeng
pushed a commit
to yanjundeng/sonic-buildimage
that referenced
this pull request
Apr 23, 2025
Why I did it When building libnl3 inside a container with a newer kernel (such as what is used on Ubuntu 24.04), some commands to create a private network namespace may fail due to restrictions. This was seen in libnl3's own Github Actions CI, and is now seen on build machines running Ubuntu 24.04 as the host with kernel 6.8. Work item tracking Microsoft ADO (number only): 31902668 How I did it Backport a patch from libnl3 to handle such cases.
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
When building libnl3 inside a container with a newer kernel (such as what is used on Ubuntu 24.04), some commands to create a private network namespace may fail due to restrictions. This was seen in libnl3's own Github Actions CI, and is now seen on build machines running Ubuntu 24.04 as the host with kernel 6.8.
Work item tracking
How I did it
Backport a patch from libnl3 to handle such cases.
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)