feat: Enhance OCI runtime spec generation with user namespace support and seccomp configuration#10
Merged
Merged
Conversation
… and seccomp configuration - Added support for user namespaces, including paths for NetNS, UserNS, and MntNS. - Introduced new fields in Opts and Spec for additional container configurations. - Implemented seccomp configuration handling in the spec generation. - Updated the Generate function to accommodate new options and namespaces. - Enhanced user ID mapping logic for rootless containers, including fallback mechanisms. - Added comprehensive smoke tests for container management, volume mounting, and networking with Nginx. - Improved error handling and logging in spec generation and test cases.
|
Important Review skippedToo many files! This PR contains 174 files, which is 24 over the limit of 150. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (174)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- Changed all import paths in the internal and pkg directories to reflect the new repository structure under garnizeh. - This includes updates across various files in the cli, eld, gan, maturin, prim, shardik, tower, waystation, and specgen packages.
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
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.
This pull request introduces a new networking engine (
Beam) for managing container networks, adds its supporting configuration and test files, and updates dependencies to support CNI and testing. The most important changes include the implementation of theBeamnetworking manager, the addition of default configuration files for CNI and seccomp, and the introduction of comprehensive failure-mode tests for the new networking logic.Networking Engine Implementation:
beam.gofile ininternal/beamimplementing theBeamstruct, which manages container network namespaces and CNI integration, including support for both rootful and rootless networking modes. The implementation includes methods for attaching and detaching networks, loading default configs, and dependency injection for testing and extensibility.Configuration Files:
configs/cni-beam0.conflistfor thebeam0bridge, specifying plugin types, IPAM, and network routes.configs/seccomp-default.jsonwith a restrictive default action and a whitelist of allowed syscalls for multiple architectures.Testing and Robustness:
beam_failure_internal_test.goto test error handling in theBeamnetworking engine, covering failure scenarios for configuration loading and plugin download logic using mock implementations.Dependency Updates:
go.modto add dependencies ongithub.com/containernetworking/cni,github.com/kr/pretty, andgolang.org/x/syncfor CNI support and improved testing utilities. Also added indirect dependencies required by new features and tests. [1] [2]