ssh-container-rollout

Automate Docker container rollouts with health checks and rollback via SSH.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of rolling out new Docker container images with health verification and rollback capabilities, ensuring service continuity and reducing downtime.

Core Features & Use Cases

  • Automated Container Rollout: Execute image pulls, container stoppage, removal, and new container creation.
  • Health Verification: Post-deployment checks ensure service is healthy.
  • Rollback Mechanism: Failsafe for rolling back to previous images if new image fails verification.
  • Use Case: Ideal for rolling out new versions of microservices or application components, providing automated management and reduced risk of deployment failure.

Quick Start

Use the ssh-container-rollout skill to deploy a new Docker image to the host 'web01', using image 'ghcr.io/myorg/my-service:v2.3.0'.

Frequently Asked Questions about ssh-container-rollout

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

FAQPage Schema
How do I automate Docker container image rollout with rollback safety?

To automate Docker container rollout, this Skill handles image pulls, container stoppage and removal, new container creation, and post-deployment health verification. It automatically rolls back to the previous image if the new container fails health checks, ensuring service continuity.

What happens if a new Docker image fails health verification during deployment?

If health verification fails during a Docker container rollout, the failsafe mechanism automatically reverts deployment to the previous image. This rollback safety ensures service continuity and reduces the risk of deployment failure.

Do I need SSH access to use Docker container rollout automation?

Yes, you need SSH access to execute Docker container rollout automation. The Skill manages remote image deployment, container stoppage, and health verification, requiring both Docker and SSH access for administrative workflows in Dockerized environments.

When should I use automated container rollback for microservice deployments?

Use automated container rollback when deploying new versions of microservices or application components in Dockerized environments. It provides automated health verification and rollback safety, reducing deployment failure risk and ensuring service continuity during updates.

Can I use this rollout automation for Dockerized application components without downtime?

Yes, this rollout automation reduces downtime for Dockerized application components. By automating image pulls, container stoppage, and new container creation with health verification, it ensures service continuity and provides rollback safety if the new image fails.