2 repositorios
Configuration of the filesystem path used for Unix domain socket communication.
Distinguishing note: None of the candidates cover the simple configuration of a socket's filesystem path for daemon connection
Explore 2 awesome GitHub repositories matching devops & infrastructure · Socket Path Configurations. Refine with filters or upvote what's useful.
Microsandbox is a runtime for creating and managing lightweight, hardware-isolated virtual machines — called sandboxes — that boot directly from standard OCI container images. Each sandbox runs as its own host process with a separate kernel, filesystem, and network stack, providing process-per-sandbox isolation. The project includes a command-line tool and multi-language SDKs (Rust, TypeScript, Python, Go) for programmatic lifecycle control, and it communicates with sandbox agents over Unix sockets using a CBOR-encoded protocol. What distinguishes Microsandbox is its combination of host-manag
Establishes connections to sandbox relay sockets using direct filesystem paths.
docker-socket-proxy is an HAProxy-based security proxy that filters and controls access to the Docker API. It acts as a security layer between containers and the Docker socket to restrict API operations based on specific paths and methods. The proxy uses environment variables to enable or disable specific API endpoints and to grant or revoke permissions for various API sections. It can enforce read-only access by restricting the API to only allow GET and HEAD requests, returning a forbidden status for unauthorized actions. The project provides capabilities for path-based request filtering, c
Allows overriding the default Docker socket path via the SOCKET_PATH environment variable.