skills.rest
jal-co
jal-coCOMMUNITY
Explore all skills by this author →
Website𝕏@jalcowastakenGitHub

security-docker

Audit Dockerfiles, docker-compose manifests, and runtime deployments for security weaknesses.

7|2|Updated Jan 18, 2026
Search Tags:#security#audit#docker#secrets#best-practices#docker-compose
One-click install
npx skills add https://github.com/jal-co/jalco-opencode --skill security-docker-jal-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-docker
Source: https://github.com/jal-co/jalco-opencode/tree/main/opencode/.config/opencode/skills/security-docker
Command: npx skills add https://github.com/jal-co/jalco-opencode --skill security-docker-jal-co

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Docker configurations and containers are frequently misconfigured, leading to leaked secrets, exposed services, and insecure defaults. This Skill provides a structured security audit to identify and remediate these risks across Dockerfiles, docker-compose manifests, and runtime deployments.

Core Features & Use Cases

  • Secrets in build layers and images: detect ENV/ARG secrets and advise on runtime secrets handling.
  • Port exposure and privileged access checks: identify ports exposed to the host and privileged configurations.
  • Non-root user enforcement and multi-stage builds: recommend best practices for running as non-root and using production-ready images.
  • Pre-deployment and runtime hardening: suitable for pre-deployment audits and ongoing container hardening reviews.

Quick Start

Run the security scan against your Dockerfiles and docker-compose files to identify secrets in layers, exposed ports, and non-root privileges.

Frequently Asked Questions about security-docker

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

FAQPage Schema
How do I audit Dockerfiles for secrets and exposed ports?▼

To audit Dockerfiles for secrets and exposed ports, scan the build layers and docker-compose manifests to detect ENV/ARG variables, identify host-bound ports, and receive actionable remediation steps for runtime secrets handling.

How do I check my docker-compose configuration for privileged access?▼

Check your docker-compose configuration for privileged access by inspecting the manifests for privileged deployments and non-root user usage, enforcing container hardening best practices by identifying insecure defaults.

What is the best way to enforce non-root user usage in Docker containers?▼

The best way to enforce non-root user usage in Docker containers is to audit the Dockerfile and runtime deployment configurations, checking for non-root enforcement and advising on multi-stage builds for production-ready images.

Does this Docker security audit require ripgrep to scan build layers?▼

Yes, this Docker security audit requires the ripgrep (`rg`) dependency to efficiently scan build layers, .dockerignore files, and docker-compose manifests for leaked secrets and insecure configurations.

When do I need to inspect .dockerignore for runtime secrets handling?▼

You need to inspect .dockerignore for runtime secrets handling during pre-deployment audits and ongoing container hardening reviews to prevent sensitive files from leaking into build layers and images.

Related Skills

Explore More Software Engineering Skills→
mwguerramwguerra
35

docker-docs

Reference local Docker and Compose documentation for exact configuration patterns.

Community
Basic
IgorWarzochaIgorWarzocha
124

security-docker

Audit Dockerfiles and Docker Compose configurations for security vulnerabilities.

Community
Intermediate
xlelibertyxleliberty

docker-development

Analyze Dockerfiles and compose services for optimization and security.

Community
Advanced
Ed1s0nZEd1s0nZ
5.6k

container-security-testing

Scan Docker images and audit Kubernetes configurations for security vulnerabilities.

Community
Advanced