docker-up

Start Docker services with docker compose up and verify health.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill docker-up-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-up
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/docker-up
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill docker-up-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates bringing up a Docker development environment with docker compose up -d --build, performs health checks on all services, and provides troubleshooting guidance. It is designed to be run before test steps like /test and /test-ui to ensure a stable baseline.

Core Features & Use Cases

  • One-click dev environment startup with docker-compose up -d --build
  • Health checks for all services to ensure readiness
  • Troubleshooting guidance for startup issues
  • Intended to be run before test pipelines like /test and /test-ui

Quick Start

Run /docker-up to start the development environment and run initial health checks.

Frequently Asked Questions about docker-up

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

FAQPage Schema
How do I bring up a Docker dev environment and verify all services are healthy?

To bring up a Docker dev environment, you can run an automated startup sequence using docker-compose up -d --build. This process initializes your predefined services and performs health checks to verify readiness before you proceed with testing.

Why does my Docker Compose startup fail before running tests?

Docker Compose startup may fail due to service initialization errors or unhealthy containers. You need a standard startup sequence with health checks to identify readiness issues and provide troubleshooting guidance for your local development workflow before testing.

Do I need Docker and Docker Compose installed to automate my dev environment startup?

Yes, you need both docker and docker-compose installed to use this automation. The process relies on predefined docker-compose.yml configurations to build containers and run health checks for your local development environment.

What is the best way to troubleshoot Docker service startup issues in a dev environment?

The best way to troubleshoot Docker service startup issues is to execute a standard startup sequence that applies health checks to all containers. This isolates initialization failures and provides targeted troubleshooting guidance for your dev environment.

Can I use automated health checks to ensure Docker container readiness before running UI tests?

Yes, you can use automated health checks to ensure Docker container readiness before running UI tests. By verifying that all services are healthy post-startup, you establish a stable baseline for subsequent test pipelines like /test and /test-ui.

When should I run an automated Docker Compose build with health checks?

You should run an automated Docker Compose build with health checks before executing test steps. Applying this local development workflow ensures all services are initialized, healthy, and ready, preventing baseline environment issues from affecting your tests.