Image tags
5
latest, versioned, date-based
Custom Crawl4AI Docker Build
Operational build console
Aligned to the reference repository: image variants, build commands, health endpoints, monitoring, and release workflow.
port 11235health / ready / metrics / playgroundweekly buildsamd64 + arm64
Release snapshot
A compact operational view of the build surface
healthylatest-allamd64 / arm64
Registry target
protemplate/crawl4ai
The reference repo centers on tagged Docker artifacts, not app analytics. This console now treats the build pipeline as the product surface.
Ports
11235
Modes
default + all
/health
basic status
/ready
readiness gate
/metrics
prometheus
/playground
interactive ui
Build notes
Weekly rebuilds, explicit tags, and health endpoints are the core operational contract.
Build variants
4
default, all, torch, transformer
Recent passes
15
completed history entries
Processed bytes
60.1 MB
build-adjacent data
Available images
Tags and intended use
| Tag | Description | Size | Use case |
|---|---|---|---|
| latest-all | Full feature build | ~2.5GB | Production |
| latest-default | Minimal build | ~1.5GB | Small footprint |
| VERSION-all | Pinned full build | ~2.5GB | Version lock |
| VERSION-default | Pinned minimal build | ~1.5GB | Version lock |
| YYYYMMDD-all | Date-based build | ~2.5GB | Reproducible |
Workflow
The release model in four beats
1
Weekly builds
Scheduled at 2 AM UTC
Refreshes upstream image tags
2
Manual dispatch
gh workflow run
Supports custom branch and install type
3
Image testing
Automated after build
Validates release output
4
Publish
Push to registry
Latest, versioned, and date tags
Config focus
What matters in the reference repo
OPENAI_API_KEY
LLM features
ANTHROPIC_API_KEY
Claude support
GROQ_API_KEY
Groq support
CRAWL4AI_PORT
Exposed service port
WORKERS
Worker process count
MEMORY_LIMIT
Container memory limit
3 failed records remain in history as part of the operational audit trail.