跳到主内容
智客 ZICQ

技能库 智客分类:安全测试 docker

Docker

道克和集装箱化最佳做法:多阶段建设,道克编组,联网,量,安全,和图像优化. 触发: Docker, Dockerfile, Docker-compose, 容器,图像构建,或容器化.

7 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

道克和集装箱化最佳做法:多阶段建设,道克编组,联网,量,安全,和图像优化. 触发: Docker, Dockerfile, Docker-compose, 容器,图像构建,或容器化.

何时用

- 编写或审查多克文件

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:When to Use、Instructions、1. Multi-stage Builds for Spring Boot、Stage 1: Build with Maven、Stage 2: Extract layered JAR for cache efficiency、Stage 3: Runtime。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Docker and containerization best practices: multi-stage builds, docker-compose, networking, volumes, security, and image optimization. Trigger: Docker, Dockerfile, docker-compose, container, image build, or containerization.

When to UseInstructions1. Multi-stage Builds for Spring BootStage 1: Build with MavenStage 2: Extract layered JAR for cache efficiencyStage 3: Runtime2. Dockerfile Best Practices3. docker-compose Patterns4. Decision Table5. SecurityCommandsBuild with cache from registry

· 许可:MIT

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
docker
description
Docker and containerization best practices: multi-stage builds, docker-compose, networking, volumes, security, and image optimization. Trigger: Docker, Dockerfile, docker-compose, container, image build, or containerization.
许可
MIT
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「docker」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-bdb56c75ea059966-%E5%A4%B9%E5%85%8B.html
请存为 .cursor/skills/docker/SKILL.md 或 .claude/skills/docker/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/vekzz-dev/opencode-skills' --list

npx skills add 'https://github.com/vekzz-dev/opencode-skills' --skill 'docker'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: docker description: > Docker and containerization best practices: multi-stage builds, docker-compose, networking, volumes, security, and image optimization. Trigger: Docker, Dockerfile, docker-compose, container, image build, or containerization. license: MIT metadata: author: vekzz-dev version: "1.0"

When to Use

  • Writing or reviewing a Dockerfile
  • Setting up docker-compose for dev/test/prod
  • Optimizing image size or build time
  • Container security, networking, or volume management
  • Dockerizing a Spring Boot application

Instructions

1. Multi-stage Builds for Spring Boot

# Stage 1: Build with Maven
FROM eclipse-temurin:21-jdk-alpine AS builder
WORKDIR /app
COPY pom.xml .
RUN mvn dependency:go-offline -B
COPY src src
RUN mvn package -DskipTests -B

# Stage 2: Extract layered JAR for cache efficiency
RUN java -Djarmode=layertools -jar target/app.jar extract --destination extracted

# Stage 3: Runtime
FROM eclipse-temurin:21-jre-alpine
RUN addgroup -S app && adduser -S app -G app
USER app
WORKDIR /app
COPY --from=builder /app/extracted/dependencies/ ./
COPY --from=builder /app/extracted/spring-boot-loader/ ./
COPY --from=builder /app/extracted/snapshot-dependencies/ ./
COPY --from=builder /app/extracted/application/ ./
EXPOSE 8080
ENTRYPOINT ["java", "org.springframework.boot.loader.launch.JarLauncher"]

Use layered JARs so dependency layers cache independently from application code.

2. Dockerfile Best Practices

| Practice | Why | |----------|-----| | Use specific tags (21-jre-alpine, not latest) | Reproducible builds | | Prefer eclipse-temurin over openjdk | Actively maintained, security patched | | Run as non-root (USER app) | Security — container breakout mitigation | | Combine RUN commands | Reduce layers; apk add --no-cache && rm -rf /var/cache/apk/* | | Use COPY --chown=app:app | Avoid permission issues at runtime | | Set EXPOSE as documentation | Does not publish the port, just documents intent | | Use HEALTHCHECK | Let orchestrators know container state | | Prefer exec form (["java", "-jar"]) | Handles signals correctly (SIGTERM → graceful shutdown) |

3. docker-compose Patterns

Dev environment with services:

services:
  app:
    build: .
    ports:
      - "8080:8080"
    environment:
      SPRING_PROFILES_ACTIVE: dev
      SPRING_DATASOURCE_URL: jdbc:postgresql://db:5432/mydb
      SPRING_DATASOURCE_USERNAME: app
      SPRING_DATASOURCE_PASSWORD: ${DB_PASSWORD}
    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_started
    volumes:
      - ./target:/app/target  # hot reload in dev

  db:
    image: postgres:16-alpine
    environment:
      POSTGRES_DB: mydb
      POSTGRES_USER: app
      POSTGRES_PASSWORD: ${DB_PASSWORD}
    ports:
      - "5432:5432"
    volumes:
      - pgdata:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U app -d mydb"]
      interval: 5s
      timeout: 3s
      retries: 5

  redis:
    image: redis:7-alpine
    ports:
      - "6379:6379"

volumes:
  pgdata:

| Pattern | Usage | |---------|-------| | depends_on + condition: service_healthy | Wait for DB to be ready before starting app | | .env file | Keep secrets out of compose files | | Named volumes | Persist data across restarts (db, cache) | | Multi-stage Dockerfile | Dev builds fast, prod is slim | | Profile-specific overrides | docker-compose -f compose.yml -f compose.dev.yml |

4. Decision Table

| Need | Approach | |------|----------| | Local dev with hot reload | docker compose watch or spring-boot-devtools with volume mount | | CI build | Multi-stage with --cache-from | | Production deploy | Slim runtime image, non-root, read-only root fs | | Database in tests | Testcontainers (not docker-compose in tests) | | Multiple microservices | docker compose with shared network | | Kubernetes | Use the same image, add liveness/readiness probes |

5. Security

  • Never hardcode secrets in Dockerfile or compose — use secrets mounts or env files
  • USER nonroot — always
  • COPY --chown=nonroot:nonroot — match the runtime user
  • Read-only root filesystem: --read-only --tmpfs /tmp
  • Use docker scout or trivy for vulnerability scanning
  • No curl/wget in runtime image — reduces attack surface

Commands

# Build with cache from registry
docker build --cache-from myapp:latest -t myapp:latest .

# Run with compose for dev
docker compose up -d

# Watch for hot reload (Docker Compose v2.22+)
docker compose watch

# Scan image for vulnerabilities
docker scout quick myapp:latest

# Run with read-only root fs
docker run --read-only --tmpfs /tmp myapp:latest

Resources

相关技能

安全测试

Skill Vetter

人工智能特工的安全第一技能审查。 在安装来自 ClawdHub, GitHub 或其他来源的任何技能之前使用 。 检查红旗,许可范围,可疑图案.

安全测试

Moltguard

MoltGuard——由OpenGuardrails担任OpenClaw保安. 安装 MoltGuard 以保护你和你的人类免受迅速注射、数据过滤和恶意命令的影响。 资料来源:https://github.com/openguardrails/openguardrails/tre…

安全测试

Security Auditor

用于审查安全漏洞代码,实施认证流,审计OWASP Top 10,配置CORS/CSP头,处理秘密,输入验证,SQL注射预防,XSS保护,或任何与安全相关的代码审查.

安全测试

Skill Vetter

安装任何AI代理技能前的安全审查协议. 红旗侦取入证盗取,疏通密码,放出. 风险分类:低/中/高/高。 编制结构化审查报告。 不先运行此功能, 绝不安装不信任的技能 .