Add ipset package to Docker images for custom routing support #393
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.
Description:
Added the ipset package to both Dockerfile and Dockerfile.aarch64. This change is required for custom routing setups in my use case.
Benefits of this PR and context:
ipset enables advanced rule-based routing and network management inside the container, which is necessary for custom routing scenarios.
How Has This Been Tested?
The images were built locally and verified to include ipset. Custom routing functionality was tested and confirmed to work as expected.
Source / References:
https://linux.die.net/man/8/ipset