github-starred/awesome-compose
2
0
Fork 0
mirror of https://github.com/docker/awesome-compose.git synced 2026-05-06 10:36:14 -05:00
Code Issues 3.3k Packages Projects Releases Wiki Activity

[PR #668] Add pentest stack - Security testing Docker Compose sample #4548

New Issue
Open
opened 2026-04-21 06:05:59 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-21 06:05:59 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/docker/awesome-compose/pull/668
Author: @bad-antics
Created: 2/4/2026
Status: 🔄 Open

Base: master ← Head: add-n01d-pentest-stack

📝 Commits (1)

  • ddbb25d Add pentest stack - Security testing environment

📊 Changes

3 files changed (+145 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)
➕ n01d-pentest-stack/README.md (+71 -0)
➕ n01d-pentest-stack/compose.yaml (+73 -0)

📄 Description

Description

Adds a new penetration testing stack sample to the Single service samples section.

What's included

This compose sample provides a complete security testing environment:

Service Image Purpose
Kali Linux kalilinux/kali-rolling Full security testing distro
Metasploit metasploitframework/metasploit-framework Exploitation framework
PostgreSQL postgres:15-alpine MSF database backend
Burp Suite portswigger/burp-suite-community Web app security proxy
Nuclei projectdiscovery/nuclei Vulnerability scanner

Features

  • Shared network for all containers
  • Shared data volume for file transfer between tools
  • Persistent storage for all tool configurations
  • Pre-configured MSF database connection

Testing

Tested on:

  • Docker Desktop 4.37 (macOS, Windows)
  • Docker Engine 24.x (Linux)
  • Docker Compose v2.x

Checklist

  • Follows contribution guidelines
  • compose.yaml uses Compose Specification
  • README.md includes usage instructions
  • All images are from official/trusted sources
  • Sample is documented in main README.md

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/docker/awesome-compose/pull/668 **Author:** [@bad-antics](https://github.com/bad-antics) **Created:** 2/4/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `add-n01d-pentest-stack` --- ### 📝 Commits (1) - [`ddbb25d`](https://github.com/docker/awesome-compose/commit/ddbb25db8a143974867ed0a3f723199413c86442) Add pentest stack - Security testing environment ### 📊 Changes **3 files changed** (+145 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) ➕ `n01d-pentest-stack/README.md` (+71 -0) ➕ `n01d-pentest-stack/compose.yaml` (+73 -0) </details> ### 📄 Description ## Description Adds a new penetration testing stack sample to the Single service samples section. ## What's included This compose sample provides a complete security testing environment: | Service | Image | Purpose | |---------|-------|---------| | Kali Linux | kalilinux/kali-rolling | Full security testing distro | | Metasploit | metasploitframework/metasploit-framework | Exploitation framework | | PostgreSQL | postgres:15-alpine | MSF database backend | | Burp Suite | portswigger/burp-suite-community | Web app security proxy | | Nuclei | projectdiscovery/nuclei | Vulnerability scanner | ## Features - Shared network for all containers - Shared data volume for file transfer between tools - Persistent storage for all tool configurations - Pre-configured MSF database connection ## Testing Tested on: - Docker Desktop 4.37 (macOS, Windows) - Docker Engine 24.x (Linux) - Docker Compose v2.x ## Checklist - [x] Follows contribution guidelines - [x] compose.yaml uses Compose Specification - [x] README.md includes usage instructions - [x] All images are from official/trusted sources - [x] Sample is documented in main README.md --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-21 06:05:59 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
proposal
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#4548
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?