Docker Socket Proxy

What This Skill Does

The Docker Socket Proxy skill allows OpenClaw agents to manage remote Docker environments securely. By leveraging a tecnativa/docker-socket-proxy instance, this skill acts as a protective firewall between your agent and the Docker daemon. Instead of granting the agent root-equivalent access to the Docker socket, this integration restricts commands based on the proxy's environment variables. It enables a comprehensive suite of container operations, including lifecycle management, system monitoring, and resource inspection, all through a standardized API interface using curl and jq.

Installation

To install this skill, use the ClawHub CLI command within your terminal or OpenClaw interface:

clawhub install openclaw/skills/skills/bp602/docker-socket-proxy

Ensure that you have curl and jq installed on your host system as these are required dependencies for the script execution. You must have a docker-socket-proxy container running and reachable via TCP, with the DOCKER_PROXY_URL environment variable configured to point to your proxy instance.

Use Cases

This skill is ideal for DevOps automation, remote server management, and local development environments where agent-assisted maintenance is required. It is perfect for developers who need to quickly rotate, inspect, or troubleshoot containerized services without leaving the OpenClaw chat interface. It also serves as a robust tool for automated cleanup tasks, such as pruning unused images or stopped containers to reclaim system resources.

Example Prompts

1. "List all containers currently running on the server and check their CPU and memory usage."
2. "Restart the 'web-service' container and show me the last 50 lines of logs to ensure it started correctly."
3. "Identify any stopped containers on the host and remove them to save disk space."

Tips & Limitations

Security is paramount; ensure your Docker socket proxy configuration limits access only to the necessary API endpoints. Because this skill relies on the proxy's configuration, some modes may fail if the corresponding Docker API endpoint is disabled in your proxy settings. Always verify your DOCKER_PROXY_URL is correctly set. Performance is optimized by jq processing, but very large outputs from list-all or logs may require moderation in prompt design to keep the agent response concise.