Dockerlabs

Devtools toolkit for Docker-related workflows — check, validate, generate, format, lint, explain, convert, template, diff, preview, fix, and report on Docker configurations. All entries are logged locally with timestamps for full traceability.

Commands

Each command (check, validate, generate, format, lint, explain, convert, template, diff, preview, fix, report) works in two modes:

• No arguments: displays the 20 most recent entries from that command's log
• With arguments: records the input with a timestamp and appends to the command's log file

Data Storage

All data is stored locally at ~/.local/share/dockerlabs/. Each action is logged to its own file (e.g., check.log, lint.log, generate.log). A unified history.log tracks all operations. Use export to back up your data anytime in JSON, CSV, or plain text format.

Requirements

• bash 4+ (uses set -euo pipefail)
• Standard Unix utilities (wc, du, grep, tail, sed, date)

When to Use

• Tracking Docker configuration checks, validations, and linting results
• Logging Docker file generation, conversion, and formatting operations
• Keeping an audit trail of Docker troubleshooting and fixes
• Exporting Docker operation history for reporting or compliance
• Searching past Docker operations by keyword

Examples

# Record a Dockerfile lint result
dockerlabs lint "Dockerfile uses latest tag — pin to specific version"

# Record a validation check
dockerlabs validate "docker-compose.yml syntax OK, 3 services defined"

# Generate a template entry
dockerlabs generate "multi-stage build for Node.js app"

# View recent lint entries
dockerlabs lint

# Search for entries mentioning "nginx"
dockerlabs search nginx

# Export all data as JSON
dockerlabs export json

# Check overall health
dockerlabs status

# View summary stats
dockerlabs stats

Powered by BytesAgain | bytesagain.com | [email protected]