containers

Enforce container security and build standards for Kubernetes and CI/CD pipelines.

17|1|Updated Jun 8, 2025

Search Tags:#security #docker #containers #ci-cd #image-building

Ready to run

npx skills add https://github.com/williamzujkowski/standards --skill containers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: containers
Source: https://github.com/williamzujkowski/standards/tree/main/skills/cloud-native/containers
Command: npx skills add https://github.com/williamzujkowski/standards --skill containers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Container standards cover building, securing, and maintaining containerized applications with repeatable patterns.

Core Features & Use Cases

Image & Build Patterns: Multi-stage builds, minimal base images, non-root containers.
Security & Compliance: Scanning, least privilege, and resource limits.
CI/CD Integration: Automated builds and image promotions.

Quick Start

Build a small container image using a multi-stage Dockerfile and run a container with non-root privileges.

Frequently Asked Questions about containers

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

FAQPage Schema

How do I build a secure container image with minimal size?▼

Use multi-stage builds to reduce image size by separating build dependencies from runtime artifacts, and select minimal base images like Alpine or distroless. This approach eliminates unnecessary layers and vulnerabilities while keeping deployment packages lean.

What are container security best practices for production?▼

Run containers as non-root users, scan images for vulnerabilities before deployment, set resource limits, configure health checks, and enforce immutable infrastructure patterns. These practices enforce least-privilege access and prevent unauthorized changes at runtime.

How do I integrate container builds into CI/CD pipelines?▼

Automate image building and vulnerability scanning in CI/CD workflows, then promote validated images through registries to orchestrators like Kubernetes. This ensures repeatable, secure deployments across environments.

Why use one process per container instead of multiple services?▼

Single-process containers simplify scaling, logging, and failure isolation in cloud-native architectures. Each container handles one responsibility, making it easier to restart, monitor, and orchestrate independently.

Can I run containers with resource limits and health checks?▼

Yes. Set CPU, memory, and storage limits to prevent resource exhaustion, and define health checks so orchestrators can automatically restart failed containers. Both are essential for reliable, scalable deployments.