docker

Build, run, and optimize Docker containers for reproducible deployments.

1|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/markus41/lobbi-design-system --skill docker-markus41
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker
Source: https://github.com/markus41/lobbi-design-system/tree/main/.claude/skills/docker
Command: npx skills add https://github.com/markus41/lobbi-design-system --skill docker-markus41

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker.

What problem does it solve?

This Skill simplifies the process of packaging applications into consistent, portable containers and managing their lifecycle, ensuring reliable and efficient deployment across various environments.

Core Features & Use Cases

  • Dockerfile Best Practices: Write optimized Dockerfiles for efficient image builds and multi-stage builds.
  • Container Management: Build, run, list, inspect, and clean up Docker images and containers.
  • Multi-Platform Builds: Create images compatible with different architectures (e.g., linux/amd64, linux/arm64).
  • Use Case: Create a Dockerfile for a Python application, build its image, and run it as a container, exposing a specific port, all with a few commands.

Quick Start

Write a Dockerfile for a Python application that installs dependencies from requirements.txt and runs a Gunicorn server.

Frequently Asked Questions about docker

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

FAQPage Schema
How do I build and run a Docker container for my application?

Building a Docker container involves writing a Dockerfile with your application's dependencies, running `docker build` to create an image, then `docker run` to execute it. The Dockerfile specifies the base image, installs requirements, and sets the entry point; `docker build` layers these instructions into a reusable image, and `docker run` starts a container instance with exposed ports and environment configuration.

What are Dockerfile best practices for efficient image builds?

Efficient Dockerfiles use multi-stage builds to reduce final image size, order instructions from least to most frequently changed for layer caching, minimize layer count, and run containers as non-root users for security. Multi-stage builds compile dependencies in earlier stages and copy only artifacts to the final stage, dramatically reducing image bloat while maintaining reproducibility.

Can I build Docker images for different architectures like ARM and x86?

Yes, Docker supports multi-platform builds targeting architectures like `linux/amd64` and `linux/arm64`. Use `docker buildx` with `--platform` flags to create images compatible across different hardware, enabling seamless deployment on diverse environments from cloud servers to edge devices and Raspberry Pi.

How do I manage container lifecycle with health checks and logging?

Container lifecycle management includes defining health checks in your Dockerfile or `docker-compose`, using `docker logs` to inspect output, `docker exec` to run commands inside running containers, and `docker inspect` to examine container state. Health checks enable automatic restart policies, and logging provides visibility into application behavior and troubleshooting.

What's the difference between Docker images and containers?

A Docker image is a read-only template containing your application, dependencies, and configuration; a container is a running instance of that image with its own isolated filesystem and process space. Images are built once and reused; containers are ephemeral runtime environments created from images and can be started, stopped, and discarded.

How do I clean up unused Docker images and containers?

Use `docker prune` commands to remove unused images, containers, and networks: `docker image prune` removes dangling images, `docker container prune` removes stopped containers, and `docker system prune` cleans all unused resources. This reclaims disk space and keeps your Docker environment organized for efficient workflows.