What does this PR do?

This allows a Dockerized Hermes agent to use the docker shell backend (with Podman or Docker) by specifying /var/run/podman/podman.sock:/var/run/docker.sock or /var/run/docker.sock:/var/run/docker.sock as container mounts.

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• Just adds docker-cli to the installaed dependecnies in the container image.

How to Test

1. Use a Dockerized Hermes agent to use the docker shell backend (with Podman or Docker) with /var/run/podman/podman.sock:/var/run/docker.sock or /var/run/docker.sock:/var/run/docker.sock specified as container mounts
2. Observe that the docker shell backend functions
3. Profit

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: Container on Rocky Linux 10

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A