sc-docker

Identify Docker security issues in Dockerfiles, compose configurations, and runtime containers.

56|5|Updated Apr 8, 2026

Search Tags:#checklist #security #docker #dockerfile #container #scanning

Ready to run

npx skills add https://github.com/ersinkoc/security-check --skill sc-docker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sc-docker
Source: https://github.com/ersinkoc/security-check/tree/main/skills/sc-docker
Command: npx skills add https://github.com/ersinkoc/security-check --skill sc-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Docker configurations and runtimes often harbor subtle security misconfigurations, secrets leakage, and image-hardening gaps that raise risk across build, deployment, and runtime environments.

Core Features & Use Cases

Dockerfile and docker-compose security checks for root users, secrets handling, privilege, health checks, and recommended mitigations.
Runtime hardening checks including read-only filesystem, dropped capabilities, seccomp/AppArmor profiles, and restricted namespaces.
Use Case: A DevOps team integrates sc-docker to continuously scan a repository's Dockerfiles and compose files, then generate actionable remediation steps for CI/CD and production environments.

Quick Start

Run sc-docker to scan Dockerfiles and docker-compose files in your repository and report findings.

Frequently Asked Questions about sc-docker

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

FAQPage Schema

How do I scan a Dockerfile for security issues and secrets exposure?▼

Dockerfile security scanning identifies misconfigurations like root users, secrets exposure, and privilege escalation. It checks Dockerfiles and docker-compose configurations, then outputs actionable remediation steps for hardening your container images.

What are common Docker container security misconfigurations in production environments?▼

Docker container security misconfigurations include running as root, exposed secrets, excessive privileges, and missing runtime protections. Scanning detects these vulnerabilities in build and runtime environments, providing standardized findings for production hardening.

How do I check Docker runtime hardening configurations like dropped capabilities and read-only filesystems?▼

Docker runtime hardening checks validate read-only filesystems, dropped capabilities, seccomp profiles, and AppArmor configurations. Scanning restricted namespaces and runtime settings ensures containers are protected against privilege escalation in production.

Can I integrate Docker security checks into a CI/CD pipeline?▼

Docker security checks integrate into CI pipelines to continuously scan repository Dockerfiles and compose files. This automated scanning generates actionable remediation steps for both CI/CD and production environments.

Does Docker security scanning cover docker-compose configurations?▼

Docker security scanning covers docker-compose configurations alongside Dockerfiles. It evaluates compose files for root users, secrets handling, privilege escalation, and health checks to ensure deployment configurations meet hardening standards.

What is the best way to automate Docker image hardening checks for DevOps teams?▼

Automating Docker image hardening involves scanning Dockerfiles and compose files for misconfigurations, secrets leakage, and privilege gaps. This generates standardized findings that DevOps teams use to apply recommended mitigations across environments.