ssh-docker-events

Fetches bounded Docker CE/EE daemon lifecycle events filtered by container, action, and type via SSH.

6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-docker-events
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssh-docker-events
Source: https://github.com/Nightreaver/python-ssh-mcp/tree/main/skills/ssh-docker-events
Command: npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-docker-events

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of understanding the lifecycle events of Docker containers, images, volumes, and networks, allowing users to quickly identify and diagnose issues.

Core Features & Use Cases

  • Fetch Docker Events: Retrieve a bounded time window of Docker events for containers, images, volumes, and networks.
  • Filter Events: Apply filters to narrow down events based on container names, actions, and types.
  • Use Case: If a Docker host misbehaves, use this Skill to quickly identify recent events like container restarts, image pulls, or network changes.

Quick Start

Use the ssh_docker_events skill to fetch Docker events for the last 30 minutes from the host 'docker1'.

Frequently Asked Questions about ssh-docker-events

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track Docker container lifecycle events over a specific time window?

Track Docker container lifecycle events by fetching daemon logs over a bounded time window. This allows you to retrieve recent activities like container restarts, image pulls, or network changes to diagnose host issues.

Can I filter Docker events by container name, action, and type?

Filter Docker events by applying specific criteria for container names, actions, and types. This narrows down the retrieved daemon logs to isolate exact lifecycle changes for containers, images, volumes, or networks.

What do I need to fetch Docker daemon events for network and volume monitoring?

Fetching Docker daemon events requires the 'docker' command availability and Python for parsing JSON output. These dependencies allow you to retrieve and read lifecycle logs for network and volume monitoring.

Why does my Docker host misbehave after recent container restarts or image pulls?

Docker host misbehavior can be diagnosed by reviewing recent lifecycle events. Fetching daemon logs helps you identify specific actions like container restarts, image pulls, or network changes that occurred before the issue.

Are there limitations to monitoring Docker events using Python and the docker command?

Monitoring Docker events is limited to a bounded time window and requires both the 'docker' command and Python. It parses JSON output to track container, image, volume, and network lifecycles rather than providing real-time continuous streaming.