 8d9b62daf3
			
		
	
	8d9b62daf3
	
	
	
		
			
			This commit implements Phase 2 of the CHORUS Task Execution Engine development plan, providing a comprehensive execution environment abstraction layer with Docker container sandboxing support. ## New Features ### Core Sandbox Interface - Comprehensive ExecutionSandbox interface with isolated task execution - Support for command execution, file I/O, environment management - Resource usage monitoring and sandbox lifecycle management - Standardized error handling with SandboxError types and categories ### Docker Container Sandbox Implementation - Full Docker API integration with secure container creation - Transparent repository mounting with configurable read/write access - Advanced security policies with capability dropping and privilege controls - Comprehensive resource limits (CPU, memory, disk, processes, file handles) - Support for tmpfs mounts, masked paths, and read-only bind mounts - Container lifecycle management with proper cleanup and health monitoring ### Security & Resource Management - Configurable security policies with SELinux, AppArmor, and Seccomp support - Fine-grained capability management with secure defaults - Network isolation options with configurable DNS and proxy settings - Resource monitoring with real-time CPU, memory, and network usage tracking - Comprehensive ulimits configuration for process and file handle limits ### Repository Integration - Seamless repository mounting from local paths to container workspaces - Git configuration support with user credentials and global settings - File inclusion/exclusion patterns for selective repository access - Configurable permissions and ownership for mounted repositories ### Testing Infrastructure - Comprehensive test suite with 60+ test cases covering all functionality - Docker integration tests with Alpine Linux containers (skipped in short mode) - Mock sandbox implementation for unit testing without Docker dependencies - Security policy validation tests with read-only filesystem enforcement - Resource usage monitoring and cleanup verification tests ## Technical Details ### Dependencies Added - github.com/docker/docker v28.4.0+incompatible - Docker API client - github.com/docker/go-connections v0.6.0 - Docker connection utilities - github.com/docker/go-units v0.5.0 - Docker units and formatting - Associated Docker API dependencies for complete container management ### Architecture - Interface-driven design enabling multiple sandbox implementations - Comprehensive configuration structures for all sandbox aspects - Resource usage tracking with detailed metrics collection - Error handling with retryable error classification - Proper cleanup and resource management throughout sandbox lifecycle ### Compatibility - Maintains backward compatibility with existing CHORUS architecture - Designed for future integration with Phase 3 Core Task Execution Engine - Extensible design supporting additional sandbox implementations (VM, process) This Phase 2 implementation provides the foundation for secure, isolated task execution that will be integrated with the AI model providers from Phase 1 in the upcoming Phase 3 development. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
		
			
				
	
	
		
			51 lines
		
	
	
		
			1.4 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
			
		
		
	
	
			51 lines
		
	
	
		
			1.4 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
| // Copyright 2022 The Go Authors. All rights reserved.
 | |
| // Use of this source code is governed by a BSD-style
 | |
| // license that can be found in the LICENSE file.
 | |
| 
 | |
| //go:build loong64
 | |
| 
 | |
| package cpu
 | |
| 
 | |
| const cacheLineSize = 64
 | |
| 
 | |
| // Bit fields for CPUCFG registers, Related reference documents:
 | |
| // https://loongson.github.io/LoongArch-Documentation/LoongArch-Vol1-EN.html#_cpucfg
 | |
| const (
 | |
| 	// CPUCFG1 bits
 | |
| 	cpucfg1_CRC32 = 1 << 25
 | |
| 
 | |
| 	// CPUCFG2 bits
 | |
| 	cpucfg2_LAM_BH = 1 << 27
 | |
| 	cpucfg2_LAMCAS = 1 << 28
 | |
| )
 | |
| 
 | |
| func initOptions() {
 | |
| 	options = []option{
 | |
| 		{Name: "lsx", Feature: &Loong64.HasLSX},
 | |
| 		{Name: "lasx", Feature: &Loong64.HasLASX},
 | |
| 		{Name: "crc32", Feature: &Loong64.HasCRC32},
 | |
| 		{Name: "lam_bh", Feature: &Loong64.HasLAM_BH},
 | |
| 		{Name: "lamcas", Feature: &Loong64.HasLAMCAS},
 | |
| 	}
 | |
| 
 | |
| 	// The CPUCFG data on Loong64 only reflects the hardware capabilities,
 | |
| 	// not the kernel support status, so features such as LSX and LASX that
 | |
| 	// require kernel support cannot be obtained from the CPUCFG data.
 | |
| 	//
 | |
| 	// These features only require hardware capability support and do not
 | |
| 	// require kernel specific support, so they can be obtained directly
 | |
| 	// through CPUCFG
 | |
| 	cfg1 := get_cpucfg(1)
 | |
| 	cfg2 := get_cpucfg(2)
 | |
| 
 | |
| 	Loong64.HasCRC32 = cfgIsSet(cfg1, cpucfg1_CRC32)
 | |
| 	Loong64.HasLAMCAS = cfgIsSet(cfg2, cpucfg2_LAMCAS)
 | |
| 	Loong64.HasLAM_BH = cfgIsSet(cfg2, cpucfg2_LAM_BH)
 | |
| }
 | |
| 
 | |
| func get_cpucfg(reg uint32) uint32
 | |
| 
 | |
| func cfgIsSet(cfg uint32, val uint32) bool {
 | |
| 	return cfg&val != 0
 | |
| }
 |