Files
Nicolas Pastorello ef5c7c3f51 fix: address Docker security and stability issues from PR review
Fixes all issues raised in PR #47 review:

1. Add .dockerignore to prevent:
   - Real .env secrets baked into image layers
   - Host node_modules (glibc) overwriting alpine (musl) → ABI mismatch
   - .git, reports/, evidence/ bloating the image

2. Fix compose host-binding:
   - Remove T3MP3ST_HOST=127.0.0.1 override (was breaking port forwarding)
   - Server now binds to 0.0.0.0 in-container (DOCKER=true from Dockerfile)
   - Host mapping stays 127.0.0.1:3333:3333 for security

3. Add critical security warning in DOCKER.md:
   - Explain exposure risk of 0.0.0.0 binding + disabled Host-header guard
   - Document safe vs unsafe deployment patterns
   - Warn against network_mode: host and -p 3333:3333 without 127.0.0.1

4. Update base image:
   - node:18-alpine → node:22-alpine (Node 18 EOL)
   - Pin by digest @sha256:16e22a550... (prevent floating tag drift)

5. Fix healthcheck in compose:
   - Was always returning success (process.exit(0))
   - Now actually tests /api/health endpoint
   - Add start_period: 40s to align with Dockerfile

6. Fix port typos in DOCKER.md:
   - 3000 → 3333 in troubleshooting examples
   - Update all example snippets to node:22-alpine with digest
2026-07-08 20:34:34 -03:00

211 lines
5.0 KiB
Markdown

# T3MP3ST Docker Deployment
Run T3MP3ST in a containerized environment. The Docker setup provides a minimal Node.js runtime with persistent volumes for reports and evidence.
## Quick Start
```bash
# Build and run
docker compose up -d
# View logs
docker compose logs -f
# Stop
docker compose down
```
The API server is available at `http://localhost:3333`.
Test endpoints:
```bash
curl http://localhost:3333/api/health
curl http://localhost:3333/api/bounty/platforms
```
## Prerequisites
- Docker Engine 20.10+
- Docker Compose 2.0+
Verify installation:
```bash
docker --version
docker compose version
```
## Environment Configuration
Copy the environment template and configure API keys:
```bash
cp .env.example .env
```
Edit `.env` with your credentials:
```env
ANTHROPIC_API_KEY=sk-ant-xxx
OPENAI_API_KEY=sk-xxx
OPENROUTER_API_KEY=xxx
```
The compose file mounts `.env` into the container automatically.
## Volume Mounts
| Host Path | Container Path | Purpose |
|---|---|---|
| `./reports` | `/app/reports` | Engagement reports and findings |
| `./evidence` | `/app/evidence` | Collected evidence and artifacts |
Data persists across container restarts.
## Running Commands
Execute any npm script inside the container:
```bash
# CLI
docker compose exec app npm run dev
# Setup
docker compose exec app npm run setup
# Doctor check
docker compose exec app npm run doctor
# Verify claims
docker compose exec app npm run verify-claims
# Run benchmarks
docker compose exec app npm run cve:bench
docker compose exec app npm run cloud:bench
docker compose exec app npm run mobile:bench
```
## Development Mode
For live code changes, mount the source directory:
```yaml
# docker-compose.dev.yml
services:
app:
build: .
volumes:
- ./src:/app/src
- ./scripts:/app/scripts
- ./reports:/app/reports
- ./evidence:/app/evidence
command: npm run dev
```
Run with:
```bash
docker compose -f docker-compose.yml -f docker-compose.dev.yml up
```
## Build Optimization
The default `Dockerfile` is single-stage for simplicity. For production, consider a multi-stage build:
```dockerfile
FROM node:22-alpine@sha256:16e22a550f3863206a3f701448c45f7912c6896a62de43add43bb9c86130c3e2 AS builder
WORKDIR /app
COPY package*.json tsconfig.json ./
RUN npm ci
COPY . .
RUN npm run build
FROM node:22-alpine@sha256:16e22a550f3863206a3f701448c45f7912c6896a62de43add43bb9c86130c3e2
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY package*.json ./
CMD ["npm", "start"]
```
This reduces final image size from ~800MB to ~300MB.
## Troubleshooting
### Container exits immediately
Check logs for startup errors:
```bash
docker compose logs app
```
Verify `.env` file exists and contains valid API keys.
### Permission errors on volumes
Ensure the host directories are writable:
```bash
mkdir -p reports evidence
chmod 755 reports evidence
```
On Linux, match container UID/GID if needed:
```bash
sudo chown -R $(id -u):$(id -g) reports evidence
```
### Port 3333 already in use
Change the host port in `docker-compose.yml` (keep the `127.0.0.1:` prefix for security):
```yaml
ports:
- "127.0.0.1:8080:3333" # host:container
```
## Cleanup
Remove containers and volumes:
```bash
docker compose down -v
```
Remove the image:
```bash
docker rmi t3mp3st-app
```
Full cleanup (use with caution):
```bash
docker system prune -a --volumes
```
## Security Notes
**⚠️ CRITICAL: External Exposure Risk**
The Docker setup binds the server to `0.0.0.0` inside the container to allow port forwarding. This disables the Host-header/DNS-rebinding guard in `server.ts`.
**SAFE:** The default `docker-compose.yml` publishes the port as `127.0.0.1:3333:3333`, which restricts access to localhost only.
**UNSAFE:** Running `docker run -p 3333:3333` (without the `127.0.0.1:` prefix) or `network_mode: host` exposes the **unauthenticated command-executing API** on all network interfaces (0.0.0.0), allowing anyone on your network (or the internet if port-forwarded) to execute arbitrary system commands.
**Deployment Rules:**
- ✅ Always bind to `127.0.0.1` on the host: `-p 127.0.0.1:3333:3333`
- ✅ Use a reverse proxy (nginx, Caddy, Coolify) with authentication for external access
- ❌ Never use `network_mode: host` in untrusted networks
- ❌ Never publish to `0.0.0.0` without authentication middleware
**Additional Security:**
- Container runs as root by default. For production, add a non-root user in the Dockerfile.
- The `.env` file is excluded from the image via `.dockerignore` to prevent secret leakage.
- Network mode is `bridge` by default (isolated from host network).
## Integration with Tools
External security tools (nuclei, ffuf, sqlmap) can run in separate containers or be installed in a custom Dockerfile:
```dockerfile
FROM node:22-alpine@sha256:16e22a550f3863206a3f701448c45f7912c6896a62de43add43bb9c86130c3e2
RUN apk add --no-cache nmap nuclei ffuf
# ... rest of Dockerfile
```
Refer to `docs/INSTALL_MATRIX.md` for the full tool list.